On 2021-11-01, [email protected] <[email protected]> wrote: > On 11/1/21 4:47 PM, Grant Edwards wrote: >> On 2021-11-01, [email protected] <[email protected]> wrote: >> >>> I format external nvme SSD (M.2) drive as NTFS on Windows (to store >>> some pictures etc.) But when I insert the drive on Linux box (it >>> has support for NTFS enabled) I get an error: >> >> Please define what you mean by "it has support for NTFS enabled". >> >> Are you running a v5.15 kernel with the new in-tree NTFS driver? >> >> Are you using the ntfs3g FUSE driver? >> >> Are you using the old, read-only NTFS in-tree driver? > > I'm using kernel: 5.4.72-gentoo > > Under: File systems: > DOS/FAT/NT Filesystems: > <*> MSDOS fs support > - <*> VFAT (Windows-95) fs support > - <*> NTFS file system support > - [*] NTFS write support > After installing sys-fs/ntfs3g > It keeps telling I don't have: > CONFIG_FUSE_FS: is not set when it should be.
OK, that's what is referred to as the old read-only in-tree driver. It has had experimental write support for a long time, but people still call it "the read-only driver". Most people "in the know" seem to advise that the write support should not be used, and many advise not using that driver it at all. The ntfs-3g FUSE driver is usually recommended instead. > I think I need to enable: >< > FUSE (Filesystem in Userspace) support You need that if you want to use the ntfs-3g FUSE driver. IIRC, the ntfs-3g driver supports a number features that the old in-tree read-only driver (which you are using) does not. The "windows_name" option appears to be one of those. If you want to use the windows_name option, you'll probably have to disable the in-tree driver and use the ntfs-3g one. It might be possible to use ntfs-3g without disabling the in-tree driver, but that sounds like a good way to get confused... -- Grant
