• SteveTech@programming.dev
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    2 months ago

    I’ve had bad experiences with ntfs3 anyway, so it’s probably for the best that ntfs-3g is the default. Also last I checked ntfs3 had effectively been orphaned by paragon (the developers), is that still the case?

    • d3Xt3r@lemmy.nzM
      link
      fedilink
      arrow-up
      14
      ·
      2 months ago

      ntfs3 has had several improvements in 6.2 and 6.8, and it’s been pretty stable for me of late. I use it to share/backup my Steam game library mainly + for my portable drives for general data storage/local backups, and haven’t had any issues.

      It’s not orphaned. There was a bit of lull after it was introduced in kernel 5.15, and yes it was a bit unstable in the 5.x series, but it’s been pretty good since 6.2 where they finally introduced the nocase and windows_names mount options. The performance improvements are worth it if you use NTFS heavily, so I would personally recommend switching.

      • Sina@beehaw.org
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        2 months ago

        I would have loved to take that performance before I converted my data drives to ext4, however it’s just inherently not stable.

        Sometimes If you have a power loss you have to run chkdsk on Windows to get out of ro mode, no?

        • d3Xt3r@lemmy.nzM
          link
          fedilink
          arrow-up
          5
          ·
          2 months ago

          There’s no need to run chkdsk from Windows, you can run ntfsfix directly from Linux:

          sudo ntfsfix /dev/path --clear-dirty
          
        • d3Xt3r@lemmy.nzM
          link
          fedilink
          arrow-up
          1
          ·
          2 months ago

          It’s r/w, if you specify the filesystem type as ntfs3. I believe if you use just ntfs it’ll be read-only, to mimic the behaviour of the old driver, for compatibility reasons.