Re: Ntfs3 keeps corrupting my ntfs partitons

No. Well, maybe. I was attempting to give some background into reasons why the NTFS3 kernel module is often accused, whereas common misunderstanding is frequently a factor. Thus the reference to “mount”.

I can’t possibly know the cause and circumstances surrounding your apparent corruption. Again, see the comment above. However, that it never happened again using NTFS-3G is hardly conclusive. My personal opinion is that NTFS filesystems should never be used in Linux; that said, I do use them myself, sparingly (in multiboot scenario’s with Windows).

Well, I wasn’t, but it looks like you’re attempting to paint it in that frame.

NTFS-3G is a user space package. To the best of my knowledge, it is not and cannot be (in its current form) included in the kernel - NTFS3, however, is a kernel module (driver). Nonetheless, NTFS-3G was the default driver for NTFS for time, as I now understand it, although my previous understanding was that it was the free variant of a separate Paragon offering to the community. It can get confusing when tracing the respective histories.

Now, that’s not only out of context, but also, just plain silly.

I think you are confused. NTFS is not my ‘preferred FS’.

Neither NTFS3 or NTFS-3G are filesystems - they are both drivers for the NTFS filesystem - there is a great difference.

I’m uncertain just what you’re attempting to communicate here. ‘Blame yourself’ was used in a casual and non-belligerent manner. Your accumulated inputs to this thread clearly show that you were not seeking support, but simply adding your own opinion to the mix; and, that’s fine. However, please do not represent that you were asking for support (when you were not) while spouting this nonsensical rubbish in the process.

Cheers.

While I don’t much like using NTFS in a multiboot scenario, I have to agree with you. I have never encountered any issues with NTFS (using the NTFS3 driver) that were not the direct result of something else; for example, a temporary hardware failure, a hard reset, failure to disable Fast Startup in Windows, ignorance or just plain stupidity. I can setup a multiboot system built-to-order, but I can never guarantee what a user might do with it afterwards. :cowboy_hat_face:

I have also never known the NTFS3 driver to cause the supposed corruption that some speak of, nor have I seen any confirmed bugs. :man_shrugging:

Most of my externals are either NTFS or EXFAT formatted (as purchased). I admit, I’m concerned about that, to some extent; but more due to the quality of the respective controllers than the filesystem. Some of them can fail if you fart.

Cheers.

1 Like