On 11/1/21 4:47 PM, Grant Edwards wrote:

On 2021-11-01, thelma@sys-concept.com <thelma@sys-concept.com> 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.

I think I need to enable:
< > FUSE (Filesystem in Userspace) support

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2021-11-01, thelma@sys-concept.com <thelma@sys-concept.com> 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?

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2021-11-01, thelma@sys-concept.com <thelma@sys-concept.com> wrote:

On 11/1/21 4:47 PM, Grant Edwards wrote:

On 2021-11-01, thelma@sys-concept.com <thelma@sys-concept.com> 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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Monday, 1 November 2021 23:09:36 GMT Grant Edwards wrote:

On 2021-11-01, thelma@sys-concept.com <thelma@sys-concept.com> wrote:

On 11/1/21 4:47 PM, Grant Edwards wrote:

On 2021-11-01, thelma@sys-concept.com <thelma@sys-concept.com> 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.

Best to disable the in-kernel write support. There was a warning it could corrupt a fs, unless you were overwriting an existing file with another file
of exactly the same size.

I think I need to enable:
< > FUSE (Filesystem in Userspace) support

You need that if you want to use the ntfs-3g FUSE driver.

Yes.

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

Have a look here, which explains what is needed for ntfs-3g:

https://wiki.gentoo.org/wiki/NTFS

PS. I recall a case where a corrupted NTFS, I think it was on Win2000, could be read by the in-kernel driver. Neither the native MSWindows OS could read it, nor the ntfs-3g.
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmGA/XYACgkQseqq9sKV Zxm9JhAAkkbz4nHX6FHJXgmuq3a0oHg/6jxXFnMdmQa3hf13ex/DB+3941X7z9b5 dTWgkQ2JK8t4OLgmj8JsjRa7C4PzLRWULdaIYiw3LQAz5FCpBmPHK4b8JJOaa/AL T4QujD1KJw11ZHqNwjIv0rnJIzYFvs2J1l4kTBK7l3Jud9zcN0g2vCOgeMBGHGpk SUymc95/fYK+Ym+z9qGrqHVJWWQqMjav5ZbxglG1bLCs35bw/rr25fYNVs9Uz4jj OjaijxZmg2hWxoc7hwNnVH/hw+kBflonssPnagi5biZizHV2vEGvG59UeoAynDs5 getn+MNe5FXysrRYmDaelmzO5IrNHdbMxVPVbace6Vrv7XzEihPAtHnLk6FyZCGA 3M7qpL7kPxY329Pu27ENy+fC1lF+rDbZhbAFoYo3adAeCM3Ft1xkylgsmN0w8j9w VUDujfhV+ksnoIOSlvfpjqMxA8YZJsAsn8aBizzun44zhX8UtLlCv8WkH7VDWpJP 8icVFGCUVISiaTp4M2V4wW6k1cpOILN6ACwSsv0iSfNTgpWVpbbLtWsnkPh1z47K z8BJ0h464tHll/j9KFbJdSYasZbJWXtvhLtpKRoaiuvuhcoqTyZ0c/FNIXUIq2Yt bbIj9h/fxZ9YdMm3P1ckZxg08XpDrXVELLkXsZXvAgj4nHaIBAc=
=z4Ub
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2021-11-04, Laurence Perkins <lperkins@openeye.net> wrote:

Because it is read-only for all practical purposes. Unless there's
been a recent improvement its write support technically works, but
it can only change the contents of existing files and cannot create
new ones. Works fine for a read-only driver, but not much point to
using it unless you're an insane nutjob like me who occasionally
needs to boot from NTFS and so needs a driver that can be compiled
in.

You've piqued my curiosity -- how do you end up needing to boot from NTFS?

[It never occurred to me that would even be possible.]


--
Grant

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)