Modified time is not updated, incompatibility with MEGASync

[Darell Collin]

I'm using v1.21 on Ubuntu 17.10. I'm using a file container.
I notice that whenever I add/delete file(s) from the file container, after I dismount it, the modified time (mtime) of the file container is not updated, even though the hash has changed. It remains the same as the creation time.

I suspect this might be the cause of incompatibility with MEGASync. The backup software always fail to detect any changes in the file container. It somehow assume the current version is older and replace the file container with previous version whenever I resume sync.

I think MEGASync relies on changes in size and timestamp. The size of a file container is always the same. The mtime of the file container doesn't update as well.

If only MEGASync use hash, then I don't think it will have any issue with the file container.

Anyone can clarify on the mtime?

[Andreas Boehlk]

Adjust setting for preserving modification timestamp..

Andreas

[Darell Collin]

Thanks. After some googling around, it seems like a common issue date back from TrueCrypt. Perhaps it should be in the FAQ or mention "Disable this if you are using cloud sync/backup" beside the setting.

[Andreas Boehlk]

You must not forget that the preservation of the container date is an important feature for plausible denyability i.e. an important security feature.

Andreas