You are not logged in.
I don't know what driver to blame: ntfs3 or ntfs-3g.
Entering "mount" into an interactive shell when the FS was mounted will tell ![]()
(Well, at least what you're using right now)
Most probably some time system hanged/crashed and I was unable to safely unmount the drive.
You should™ always run chkdsk on windows when something like this happens
Beside that drive with ntfs filesystem … With second drive
So what filesystem is on that second drive?
the name of the folder was changed.
Can you tell from what to what name?
Offline
Second drive also had ntfs filesystem, from beginning and I didn't changed that because I sometimes connect it to windows. Folder name was Python and later I copied file python, so both were in the same folder named Documents. I done this in Linux, some time passed, I forgot about it, do backup and some day connect drive to windows...
And when corruption on first drive happened years ago, I don't remember what driver was displayed by mount. Maybe just fuseblk? I didn't know when it happened - find out when was coping files. For finding out that type of errors some procedures had to be done and for test drives; in real life no one will find it immediately, so won't know what done that corruption exactly.
Last edited by xerxes_ (Yesterday 19:59:53)
Offline
I know that there's some special code in udisks that will prefer ntfs3 that AFAIK only triggers when ntfs-3g's compat symlinks are present, so I'm trying to identify whether you were actually running ntfs3 as that has been known for quite a few corrupting factors
I found https://github.com/storaged-project/udisks/pull/985 that replaced a nonfunctional hardcoded preference for ntfs3 with a config option. It's documented at https://storaged.org/udisks/docs/mount_options.html that the default is "ntfs_drivers=ntfs3,ntfs", and indeed in testing on my machine, udisksctl without "-t ntfs" will use ntfs3. That probably means I've used ntfs3 some of the time, though I seem to have dodged any problems in it.
Offline
Folder name was Python and later I copied file python
Unlike ntfs, win32 is not case sensitive.
https://man.archlinux.org/man/ntfs-3g.8#ignore_case
Also see https://man.archlinux.org/man/mount.8#M … s_for_vfat
Idk how https://docs.kernel.org/filesystems/ntfs3.html handles this but is a major trap when sharing files between windows and linux (and technically not even FS-related)
Offline
Ok, suggestion rejected
. I see what you guys mean by providing relevant logs etc., the thing is, I do not have comfort of corrupting drive again, further, I do not have that issue since ntfs-3g is removed from the system, so for me at least, it is quite obvious what the cause of the issue is, it's not cosmic rays
, it's bad software. I can only hope that people who face same issue would have the comfort and time to do all the work required to actually address the issue that is real and not imaginary, making the software better.
I wish I could be of more help, sadly that is not the case.
Offline
since ntfs-3g is removed from the system
https://en.wikipedia.org/wiki/Coincidence
https://en.wikipedia.org/wiki/Correlation
https://en.wikipedia.org/wiki/Causation
it's bad software
Yes, but a lot of the ntfs3 issues where fixed - that's why it's less prone to corrupt your files.
You essentially only need to answer two questions:
1. Were you mounting the partition w/ a manual mount command or fstab entry and explicitly selected ntfs-3g there or did you mount the drive by clicking on some icon in a file browser or a popup from your desktop?
2. If the answer to the above is "icon in a file browser or a popup", did you explicitly change the udisks configuration to prefer ntfs over ntfs3?
If the answers to those questions are "icon in a file browser or a popup" and "no" you have never been using ntfs-3g in the first place
You can verify that by installing it, mounting the partition and check the output of "mount"
Offline