When my Windows partition is mounted in Fedora 41 KDE, its not properly working. With /etc/fstab, the partition is either read-only (type = auto or ntfs-3g) or with the dropbox folder non accessible (type = ntfs3), displayed as a link which gives an error. The same partition is working nicely from KDE Neon. It worked correctly until about a month ago. Reproducible: Always Steps to Reproduce: 1. mount the ntfs partition Actual Results: the partition is not working correctly. Expected Results: file in the partition are read/write and Dropbox folder works as well
> With /etc/fstab, the partition is either read-only (type = auto or ntfs-3g) The usual cause is Windows not to have been fully shut and left hibernated. On a dual-boot system boot into Windows and leave it through "restart" instead of "shut down". On an external drive mount into Windows and apply the unplug procedure. Anyway, what was the mounting message ? Note : AFAIK ntfs3 is not supported through bugzilla.
For a dual boot system I should have added you can get a permanent full closing of Windows by issuing as an Administrator the command powercfg /h off
As mentioned, mounting this partition in the same condition works fine with KDE Neon et has worked for months in Fedora. So it's not a problem of Windows. For mounting I modified /etc/fstab as is : UUID=7CB61175B61130DE /mnt/ntfs ntfs-3g defaults,nofail,x-systemd.automount 0 2 I don't get any message when login.
When you mount through /etc/fstab, the mount messages are shown in syslog. It may be easier to get them by mounting from CLI : sudo ntfs-3g -o rw /dev/disk/by-uuid/7CB61175B61130DE /mnt/ntfs
With this commande, there is no message shown. The partition is mounted, but the Dropbox folder is not accessible (displayed as a link which gives an error).
I would need to know what kind of symlink is used in your situation. ntfs-3g supports several modes (interix, WSL, and several native Windows modes), but Windows cross-device links rely on device letters which ntfs-3g cannot translate without extra information (details in https://github.com/tuxera/ntfs-3g/wiki/Junctions-Points,-Symbolic-Links-and-Reparse-Points How was this link created ? If this is a Windows cross-device link, you can define the device letter in .NTFS-3G. To check whether this is your situation, please post the output of getfattr -h -e hex -n system.ntfs_reparse_data the-path-to-link
the link appears when the partition is mounted with the command.
the output of the getfattr command for the link is : system.ntfs_reparse_data=0x1af000906c00000001006c0046655270d6f189f76800000002000a0007000100600000000a000400640000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001000000f6000000
This is a link to a remote cloud directory which ntfs-3g cannot process.
Well, it works just fine in KDE Neon...