Current state of NTFS compatibility? - eviltoast

Hi all. I’ve used Linux off and on for almost two decades now but most recently in a VM. I’m thinking I might make the permanent switch sometime before Windows 10 EOL. My concern is that I have over 12TB of data spanned across many drives, all in the NTFS file system. How is NTFS compatibility nowadays? For a time, I remember it being recommended to mount NTFS as read only. It seems infeasible to convert my current data to a Linux filesystem. Thoughts?

Edit: I don’t have time to reply to everyone but thanks for the information and discussion. I’m looking to rearrange some things on my drives to free up one drive entirely and then perhaps give Fedora Linux another spin on a secondary drive along with Windows on another. If all goes well, maybe Windows will get the boot or um never booted again.

  • db2@lemmy.world
    link
    fedilink
    arrow-up
    3
    arrow-down
    2
    ·
    9 months ago

    Now I want to try that though. As long as it’s baked in to the kernel it should theoretically work…

    • Pantherina@feddit.de
      link
      fedilink
      arrow-up
      3
      ·
      9 months ago

      http://en.wikipedia.org/wiki/NTFS#Linux

      Lots of different drivers, basically all reverse engineered. Different actions supported, macOS doesnt give a f* and just supported read (at some time some user wrote that) and Linux had no support for some advanced functions that are unstable.

      The latter scenario could lead to a filesystem being corrupted and thus not usable, as it has no full compatibility.

      Like, it is probably possible but just no. You are using reverse engineered drivers and there are better alternatives that are more stable (nouveau, Asahi, always exceptions).

      • cmnybo@discuss.tchncs.de
        link
        fedilink
        English
        arrow-up
        6
        arrow-down
        1
        ·
        9 months ago

        The new kernel driver is a mess and isn’t really being maintained. The FUSE driver is the only one that’s actually usable and even then, it can cause corruption in certain conditions. It’s still best to mount read only whenever possible.

        • db2@lemmy.world
          link
          fedilink
          arrow-up
          4
          ·
          9 months ago

          You guys are misunderstanding the purpose, I don’t want to (necessarily) get a stable system out of it, I want to watch how it fails over time.