Hello,
The new Linux Kernal 5.15 is bringing a new driver for NTFS file system named NTFS3 from Paragon Software’s, I installed this new Kernel in my current Stable Brunch KDE and I’m curious to know if this new NTFS driver is already enabled by default or if should I run any command to enable it? How to know what is the current solution for NTFS that my kernel is running?
Thanks
Methinks you’d just have to use ntfs3 as filesystem type when mounting.
Also see
$ cat /proc/filesystems
The option NTFS3 is not available at KDE Partion Manager, so we need to wait KDE team to update the software to include NTFS3 in the list?
$ cat /proc/filesystems
In my system, the link above shows:
nodev sysfs
nodev tmpfs
nodev bdev
nodev proc
nodev cgroup
nodev cgroup2
nodev cpuset
nodev devtmpfs
nodev binfmt_misc
nodev configfs
nodev debugfs
nodev tracefs
nodev securityfs
nodev sockfs
nodev bpf
nodev pipefs
nodev ramfs
nodev hugetlbfs
nodev devpts
nodev autofs
nodev mqueue
nodev binder
nodev pstore
ext3
ext2
ext4
fuseblk
nodev fuse
nodev fusectl
squashfs
No, the file system itself is still NTFS, the file system driver is NTFS3.
In /etc/fstab, normally you’d mount it as ntfs-3g, but now you might be able to mount it as ntfs3. Don’t quote me on if ntfs3 is the correct file system mounting or not, since I haven’t looked into it enough yet.
Edit:
https://www.kernel.org/doc/html/latest//filesystems/ntfs3.html
File system type to use on mount is ‘ntfs3’.
So yes, you mount it in /etc/fstab as ntfs3.
So KDE Partion Manager doesn’t have the proper tool to define NTFS3? the only way is trough editing the /etc/fstab?
Mine is defined as NTFS so I think it’s the NTFS -3g, will try to define as NTFS3 I hope for KDE team to implement it in the partition manager, GUI is much better.
You could always bring it up to them in the forums:
/etc/fstab is super easy to edit with a text editor though.
You can even securely use GUI Text Editors instead of TUI editors (like nano or vim), by doing:
env SUDO_EDITOR="/usr/bin/kate" sudoedit /etc/fstab
Substitute kate with whatever text editor
Though I usually just do:
sudo nano /etc/fstab
Thank you, I will test it, and if it works I will sign the solution.
As said above, it is the file system you set in the KDE partition manager, it is NTFS, whatever the driver you use for mounting it is NTFS.
As mount option you can define ntfs or ntfs-3g in the fstab file (same thing, ntfs links to ntfs-3g) or now in Linux 5.15 you also have the new driver, ntfs3, all of them to support the NTFS file system.
Yes, clear ,but from user point of view I’d ratter prefer to manage this trough KDE Partition Manager not needing to go to fstab. Editing fstab with Kate is simple, but maybe preferences vary from each people, how to implement things is very tricky.
Know once you help me to how to set-up it as currently implemented i will do it and post feedback. Currently I fell NTFS very slow in Linux, so I’d like to try this new file to see if it brings some improvements.
This is not what this tool is for.
Actually you can modify the mount point but you can’t select a driver as far as I know.
Why not?
While mounting the driver, and in general it was already formatted and the file-system was already defined during the format process, It allow me to choose witch file-system to use in the drop menu, so I understand which drive I want to use, would be nice to have the NTFS3 in the list, otherwise what is the reason to offer a drop menu list? Would be better to auto recognize the file-system and lock the options to the proper one unless the driver is not formatted, so the customer can choose any file-system.
Because it wasn’t made to select file system drivers. As I said before, you can ask KDE devs to see if they are willing to do it.
That drop down menu is to select File Systems, NOT File System Drivers, there is a difference. Adding ntfs3 to that specific list would not make sense. They would have to add another section for it.
Also, the program will have to detect what kernel the user is running as well, since not every kernel has the ntfs3 driver. It also needs to detect if the user has ntfs-3g installed as well, for those who use ntfs-3g, as it is a separate package.
If it just says ntfs in /etc/fstab, I think it might mean it is using the legacy ntfs driver that is built into the kernel, not even ntfs-3g. I am not 100% sure though. I always just put it in as ntfs-3g. I assume KDE Partition Manager does it as ntfs.
As I said they are the same, unless you modify your Manjaro installation.
[omano@omano-nvme ~]$ which mount.ntfs
/usr/bin/mount.ntfs
[omano@omano-nvme ~]$ which mount.ntfs-3g
/usr/bin/mount.ntfs-3g
[omano@omano-nvme ~]$ ls /sbin/mount.ntfs* -l
lrwxrwxrwx 1 root root 16 2 sept. 19:34 /sbin/mount.ntfs -> /usr/bin/ntfs-3g
lrwxrwxrwx 1 root root 16 2 sept. 19:34 /sbin/mount.ntfs-3g -> /usr/bin/ntfs-3g
Pretty much the same on many/all distribution too as far as I know.
The last questions,
Is the fstab a single file used for all kernels? or when I log into a different kernel that file is individual for each kernel?
I’m making this questions to avoid issues if I change the file while using kernel 5.15 and log into a different one.
How many can you find?
One fstab to rule them all. 
https://wiki.manjaro.org/index.php/Fstab
This is a file for the system, there is no per kernel configuration so think about it if you want to use this driver, before switching to kernel which don’t have support for it.
I don’t understand it either. I waited until the kernel 5.15 is officially out on Manjaro.
Still there is no NTFS3
Still everything maps to the old NTFS3-G and I don’t see any NTFS driver in the kernel space either.
l /sbin/mount.ntfs*
Permissions Size User Group Date Modified Name
lrwxrwxrwx 16 root root 2 Sep 19:34 /sbin/mount.ntfs -> /usr/bin/ntfs-3g*
lrwxrwxrwx 16 root root 2 Sep 19:34 /sbin/mount.ntfs-3g -> /usr/bin/ntfs-3g*
l /lib/modules/5.15.1-1-MANJARO/kernel/fs/
Permissions Size User Group Date Modified Name
drwxr-xr-x - root root 9 Nov 09:38 9p/
drwxr-xr-x - root root 9 Nov 09:38 affs/
drwxr-xr-x - root root 9 Nov 09:38 afs/
drwxr-xr-x - root root 9 Nov 09:38 befs/
drwxr-xr-x - root root 9 Nov 09:38 btrfs/
drwxr-xr-x - root root 9 Nov 09:38 cachefiles/
drwxr-xr-x - root root 9 Nov 09:38 ceph/
drwxr-xr-x - root root 9 Nov 09:38 cifs/
drwxr-xr-x - root root 9 Nov 09:38 coda/
drwxr-xr-x - root root 9 Nov 09:38 cramfs/
drwxr-xr-x - root root 9 Nov 09:38 dlm/
drwxr-xr-x - root root 9 Nov 09:38 ecryptfs/
drwxr-xr-x - root root 9 Nov 09:38 erofs/
drwxr-xr-x - root root 9 Nov 09:38 exfat/
drwxr-xr-x - root root 9 Nov 09:38 ext4/
drwxr-xr-x - root root 9 Nov 09:38 f2fs/
drwxr-xr-x - root root 9 Nov 09:38 fat/
drwxr-xr-x - root root 9 Nov 09:38 fscache/
drwxr-xr-x - root root 9 Nov 09:38 fuse/
drwxr-xr-x - root root 9 Nov 09:38 gfs2/
drwxr-xr-x - root root 9 Nov 09:38 hfs/
drwxr-xr-x - root root 9 Nov 09:38 hfsplus/
drwxr-xr-x - root root 9 Nov 09:38 isofs/
drwxr-xr-x - root root 9 Nov 09:38 jbd2/
drwxr-xr-x - root root 9 Nov 09:38 jffs2/
drwxr-xr-x - root root 9 Nov 09:38 jfs/
drwxr-xr-x - root root 9 Nov 09:38 lockd/
.rw-r--r-- 5,3k root root 6 Nov 15:10 mbcache.ko.xz
drwxr-xr-x - root root 9 Nov 09:38 minix/
drwxr-xr-x - root root 9 Nov 09:38 netfs/
drwxr-xr-x - root root 9 Nov 09:38 nfs/
drwxr-xr-x - root root 9 Nov 09:38 nfs_common/
drwxr-xr-x - root root 9 Nov 09:38 nfsd/
drwxr-xr-x - root root 9 Nov 09:38 nilfs2/
drwxr-xr-x - root root 9 Nov 09:38 nls/
drwxr-xr-x - root root 9 Nov 09:38 ocfs2/
drwxr-xr-x - root root 9 Nov 09:38 omfs/
drwxr-xr-x - root root 9 Nov 09:38 orangefs/
drwxr-xr-x - root root 9 Nov 09:38 overlayfs/
drwxr-xr-x - root root 9 Nov 09:38 pstore/
drwxr-xr-x - root root 9 Nov 09:38 quota/
drwxr-xr-x - root root 9 Nov 09:38 reiserfs/
drwxr-xr-x - root root 9 Nov 09:38 romfs/
drwxr-xr-x - root root 9 Nov 09:38 smbfs_common/
drwxr-xr-x - root root 9 Nov 09:38 squashfs/
drwxr-xr-x - root root 9 Nov 09:38 ubifs/
drwxr-xr-x - root root 9 Nov 09:38 udf/
drwxr-xr-x - root root 9 Nov 09:38 ufs/
drwxr-xr-x - root root 9 Nov 09:38 vboxsf/
drwxr-xr-x - root root 9 Nov 09:38 xfs/
drwxr-xr-x - root root 9 Nov 09:38 zonefs/
How can I activate it now?
See
Build your own kernel where the driver is activated or wait until Manjaro Team does it in 5.15 or later series.
Another option is detailed here:
Yes, I checked the compilation profile of the kernel. I found that the NTFS3 component is not included in the 5.15 kernel of Manjaro.