From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: external (NFTS) USB 2TB stick error mount.
Date: Tue, 02 Nov 2021 08:57:26 +0000 [thread overview]
Message-ID: <4692098.31r3eYUQgx@lenovo.localdomain> (raw)
In-Reply-To: <slps3g$686$1@ciao.gmane.io>
[-- Attachment #1: Type: text/plain, Size: 2562 bytes --]
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.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-11-02 8:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 21:41 [gentoo-user] external (NFTS) USB 2TB stick error mount thelma
2021-11-01 21:50 ` Michael
2021-11-01 21:57 ` thelma
2021-11-01 21:58 ` Michael
2021-11-01 22:47 ` [gentoo-user] " Grant Edwards
2021-11-01 22:59 ` thelma
2021-11-01 23:09 ` Grant Edwards
2021-11-02 8:57 ` Michael [this message]
2021-11-04 22:38 ` Laurence Perkins
2021-11-04 22:53 ` Grant Edwards
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4692098.31r3eYUQgx@lenovo.localdomain \
--to=confabulate@kintzios.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox