[SUGGESTION] Remove ntfs-3g from the repository

seth · 2026-08-07 19:39:26

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?

xerxes_ · 2026-08-07 19:49:31

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_ (2026-08-07 19:59:53)

jbosboom · 2026-08-07 20:04:29

V1del wrote:

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.

seth · 2026-08-07 20:14:35

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)

lpr1 · 2026-08-07 21:06:56

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.

seth · 2026-08-07 22:02:28

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"

Wild Penguin · Yesterday 09:29:52

If things work out for you, that's fine, carry on. Take the advice and try to remember it for the future.

Typically, when trying to reproduce, one does not want to do it with important data but in a safe environment. Make the exact steps you think caused the bug (with safe, test data!), if it doesn't re-trigger, you are wrong about the issue. Some (well, unfortunately most) issues can be sporadic and difficult to reproduce, which means you want to back up all important data and possibly enable more verbose logging, then carry on whatever you think causes the issue, wait until it triggers.

As it's mostly established ntfs-3g is typically more stable and ntfs3 has had issues (up until this point), also considering seth's post, then if I were in your shoes, definitely back up everything important from the ntfs partition.

Last edited by Wild Penguin (Yesterday 09:30:30)

lpr1 · Yesterday 09:31:09

seth wrote:

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"

Yes, these are the answers, 1. File manager icon. 2. No further configuration.
The thing is, if ntfs-3g was never used, how did it's own removal solved the issue?

Interesting that ntfs-3g installs fuse2 package.

Last edited by lpr1 (Yesterday 09:31:27)

seth · Yesterday 11:22:56

The thing is, if ntfs-3g was never used, how did it's own removal solved the issue?

https://www.merriam-webster.com/dictionary/coincidence

Interesting that ntfs-3g installs fuse2 package.

It's a fuse driver…

Arch Linux

#26 2026-08-07 19:39:26

Re: [SUGGESTION] Remove ntfs-3g from the repository

#27 2026-08-07 19:49:31

Re: [SUGGESTION] Remove ntfs-3g from the repository

#28 2026-08-07 20:04:29

Re: [SUGGESTION] Remove ntfs-3g from the repository

#29 2026-08-07 20:14:35

Re: [SUGGESTION] Remove ntfs-3g from the repository

#30 2026-08-07 21:06:56

Re: [SUGGESTION] Remove ntfs-3g from the repository

#31 2026-08-07 22:02:28

Re: [SUGGESTION] Remove ntfs-3g from the repository

#32 Yesterday 09:29:52

Re: [SUGGESTION] Remove ntfs-3g from the repository

#33 Yesterday 09:31:09

Re: [SUGGESTION] Remove ntfs-3g from the repository

#34 Yesterday 11:22:56

Re: [SUGGESTION] Remove ntfs-3g from the repository

Board footer