Other ntfs-3g changes ctime and mtime on access

Hi. Forgive me my english.

I'm trying to work with NTFS partition using ntfs-3g(8) driver (please tell me if you know alternatives).

All seems to work fine except one thing: any access to any file on NTFS partition (even simple reading with cat <filename> command) modifies not only atime (access time), but also ctime (change time) and mtime (modify time). As a result, I can't use mtime sorting in my "downloads" dir :)

There is "noatime" option for ntfs-3g and it works but ctime and mtime are still modified.

Any ideas? If you also use ntfs-3g and don't have such problems, please tell me.

Update 1: Tuxera (driver developer) blames FreeBSD's fuse kernel module and says that he not going to fix anything.
Update 2: "Deprecated" ntfsmount from ntfsprogs package don't have such problems.
 
Last edited:
Now I have timestamps damaged on all my photos after just watching them in thumbnails mode...
Even if I missed some mounting options, I still don't understand how software with such bugs can exist with "stable version" status and how Tuxera can call it "safe".
Sorry. I know that ntfs-3g isn't part of FreeBSD. FreeBSD is cool.
 
Tuxera says that it is not ntfs-3g problem. I tried to repeat the test inside virtual machine (VirtualBox 4.3.30). NTFS partition was created and formatted from Windows 7. Nothing except FreeBSD 10.2 and ntfs-3g was installed.

ntfs.png


Are you sure it is not fuse-freebsd problem?
Someone have to do something...
 
I still don't understand how software with such bugs can exist with "stable version" status and how Tuxera can call it "safe".
Keep in mind that ntfs-3g uses a reverse engineered NTFS. There's zero documentation from Microsoft. And MS has a habit of changing NTFS details every now and then. These changes would need to be reverse engineered again before it can be implemented. But just the mere fact that it's reverse engineered means there's bound to be issues.
 
Back
Top