Aside from the introduction of a third driver for NTFS nothing has changed in decades.
Your driver choices are:
You specify which one via the -t argument to mount or in the fstype field of fstab. e.g.orYou may be hitting issues with the fact that NTFS security is not a one to one mapping to Linux security. I've no idea how you might address that as it's not something I've had to deal with. Reading the relevant documentation for mount and the three filesystem drivers may help.
Or it might be hardware related with the enclosure. I don't have one so can't check.
Is there a strong reason for using NTFS? Network clients using SMB, NFS, ftp, sftp, sshfs, etc don't care or know what the underlying file system is. The only one that do are those using iSCSI or similar block level proctcols.
Your driver choices are:
- ntfs: old and read only,
- ntfs-3g: newer, FUSE based, read/write but slower
- ntfs3: latest in kernel driver, read/write
You specify which one via the -t argument to mount or in the fstype field of fstab. e.g.
Code:
sudo mount -t ntfs-3g /dev/sda1 /mntCode:
/dev/sda1 /mnt ntfs-3g defaults 0 0Or it might be hardware related with the enclosure. I don't have one so can't check.
Is there a strong reason for using NTFS? Network clients using SMB, NFS, ftp, sftp, sshfs, etc don't care or know what the underlying file system is. The only one that do are those using iSCSI or similar block level proctcols.
Statistics: Posted by thagrol — Fri Sep 05, 2025 4:25 pm