You are not logged in.
I have one partition NTFS formatted. Mounted automatically by fstab.
One of the changes in the new kernel is going to be native support for NTFS.
Should I take any special steps during upgrade? For example, remove ntfs-3, upgrade system and reboot?
Offline
Have you read through https://bbs.archlinux.org/viewtopic.php?id=270963 ?
Last edited by loqs (2021-11-12 22:47:25)
Offline
Thank you.
I also checked udisk support
If I understand correctly, this issue is temporary (probably).
So if I would like to use new driver I should change my fstab from:
# /dev/nvme0n1p2 LABEL=WIN10
UUID=FC346C52346C11C6 /Windows ntfs rw,nosuid,nodev,user_id=0,group_id=0,allow_other,blksize=4096 0 0to
# /dev/nvme0n1p2 LABEL=WIN10
UUID=FC346C52346C11C6 /Windows ntfs3 rw,noatime,nosuid,nodev,user_id=0,group_id=0,allow_other,blksize=4096 0 0My fstab ntfs part was automatically by genfstab during system installation.
And to work with KDE Plasma I should add
ntfs_defaults=uid=$UID,gid=$GID,noatime,preallocto
/etc/udisks2/mount_options.conf in [defaults] sectionIs that correct?
Last edited by 860lacov (2021-11-13 14:12:08)
Offline
user_id=0,group_id=0,blksize=4096Are all fuse specific options. I would drop them.
udisks2 no idea, I would suggest testing it.
Offline
I tried to use ntfs3 but after fstab edition system didn't boot.
With lsmod I checked and there is no ntfs module loaded.
It is possible to load ntfs3 witch modprobe.
So if I would like to change ntfs-3g to ntfs3 then I have to loade this module with mkinitcpio ?
Offline
The module is called ntfs3 not ntfs. Have you checked the journal for anything related to the failed mount? Have you tried manually mounting with the same options you have in the fstab entry?
Offline
I didn't check the journal. After boot failure, I just restored my fstab backup.
I'm aware that the module is ntfs3
For testing purposes, I did:
Boot to working system (settings with ntfs-3g)
Unmounted Windows NTFS drive
modprobe ntfs3
Mounted NTFS drive with mount -t ntfs3
WIth something like this I had access to Windows drive.
Offline
I'm aware that the module is ntfs3
This is why you are requested to post actual outputs rather than narrative as others do not know what you are aware of. https://bbs.archlinux.org/viewtopic.php?id=57855
Offline
[jm@spin ~]$ cat Dokumenty/dmesg | grep ntfs -i
[ 7.741047] ntfs3: Max link count 4000
[ 7.741049] ntfs3: Enabled Linux POSIX ACLs support
[ 7.741049] ntfs3: Read-only LZX/Xpress compression included
[ 7.741274] ntfs3: Unknown parameter 'allow_other'
[ 8.354539] ntfs3: Unknown parameter 'allow_other'
[ 8.382619] ntfs3: Unknown parameter 'allow_other'
[ 8.398465] ntfs3: Unknown parameter 'allow_other'
[ 8.422018] ntfs3: Unknown parameter 'allow_other'
[jm@spin ~]$ cat Dokumenty/journal | grep ntfs -i
lis 14 20:32:12 spin kernel: ntfs3: Max link count 4000
lis 14 20:32:12 spin kernel: ntfs3: Enabled Linux POSIX ACLs support
lis 14 20:32:12 spin kernel: ntfs3: Read-only LZX/Xpress compression included
lis 14 20:32:12 spin kernel: ntfs3: Unknown parameter 'allow_other'
lis 14 20:32:13 spin kernel: ntfs3: Unknown parameter 'allow_other'
lis 14 20:32:13 spin kernel: ntfs3: Unknown parameter 'allow_other'
lis 14 20:32:13 spin kernel: ntfs3: Unknown parameter 'allow_other'
lis 14 20:32:13 spin kernel: ntfs3: Unknown parameter 'allow_other'Offline
[ 8.398465] ntfs3: Unknown parameter 'allow_other'Did you try with that option removed?
Offline
[ 8.398465] ntfs3: Unknown parameter 'allow_other'Did you try with that option removed?
I checked it today.
System booted but ntfs partition is read only for non root user
[jm@spin ~]$ journalctl -b | grep ntfs
lis 15 11:48:10 spin kernel: ntfs3: Max link count 4000
lis 15 11:48:10 spin kernel: ntfs3: Enabled Linux POSIX ACLs support
lis 15 11:48:10 spin kernel: ntfs3: Read-only LZX/Xpress compression included
[jm@spin ~]$ sudo dmesg | grep ntfs
[ 7.045149] ntfs3: Max link count 4000
[ 7.045152] ntfs3: Enabled Linux POSIX ACLs support
[ 7.045153] ntfs3: Read-only LZX/Xpress compression includedfstab
UUID=FC346C52346C11C6 /Windows ntfs3 rw,nosuid,nodev,noatime 0 0Last edited by 860lacov (2021-11-15 10:53:00)
Offline
You still need to specify gid and uid (... or appropriate umask/dmasks) to make it accessible to other users.
Last edited by V1del (2021-11-15 11:50:13)
Offline
You still need to specify gid and uid (... or appropriate umask/dmasks) to make it accessible to other users.
So should it be something like:
UUID=FC346C52346C11C6 /Windows ntfs3 rw,nosuid,nodev,noatime,umask=0644,dmask=755 0 0Offline
Are you confusing mask with mode permissions used by chmod?
Offline