Announcement

Collapse
No announcement yet.

Concerns Raised Over The "New" NTFS Linux Driver That Merged Last Year

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • brucethemoose
    replied
    Originally posted by caligula View Post

    Using torrents doesn't imply you're storing them on a NTFS drive. I've never done that. Then again, if it's RIAA who's asking, I've never used torrents in my life.
    I don't think its torrents specifically... perhaps random IO? I get it when batch writing or modifying thousands of little PNGs. A *few* inevitably end up corrupted, which is super annoying.

    Leave a comment:


  • Mangix
    replied
    Sounds like the war may have impacted something. Who knows.

    Leave a comment:


  • ncohafmuta
    replied
    Originally posted by caligula View Post

    Using torrents doesn't imply you're storing them on a NTFS drive. I've never done that. Then again, if it's RIAA who's asking, I've never used torrents in my life.
    mine go to a xfs ssd before being moved to ntfs. *shrug*

    Leave a comment:


  • caligula
    replied
    Originally posted by microcode View Post
    Gotta say, NTFS-3g is basically fine for most people I think. The performance is good, and I doubt there are many demanding NTFS as a boot volume filesystem on Linux.
    The performance of FUSE file systems is only good if you have don't have high demand for BW / IOPS. It might seem efficient on some old SATA HDD, but I wouldn't use a FUSE file system for PCIe 4 devices.

    Leave a comment:


  • caligula
    replied
    Originally posted by unsound View Post

    I don't think it is, many people use torrents. Has it been reported to the mailing list or in a github issue? I can't see it in the list of open issues on github. It's certainly worth investigating as it sounds quite serious.
    Using torrents doesn't imply you're storing them on a NTFS drive. I've never done that. Then again, if it's RIAA who's asking, I've never used torrents in my life.

    Leave a comment:


  • ncohafmuta
    replied
    Originally posted by bemerk View Post
    Which recently released Distros have it active by default and which still play it safe and use ntfs.3g ?
    Indirect note; as an unraid stable 6.9.2 user using NTFS media drives, we're on slackware 14.2/kernel 5.10.28-unraid/ntfs-3g 2017.3.23. Latest unraid 6.10 RC is slackware 15/kernel 5.15.30-unraid. I assume the paragon driver is in it (and this issue would concern me a little when we go stable), but i don't know for sure.

    Leave a comment:


  • ml35
    replied
    Originally posted by bemerk View Post
    Which recently released Distros have it active by default and which still play it safe and use ntfs.3g ?
    Ubuntu jammy (22.04 LTS) ships it as a module in package linux-modules-extra-*-generic (which is not installed by default on a minimal install)

    Leave a comment:


  • bemerk
    replied
    Which recently released Distros have it active by default and which still play it safe and use ntfs.3g ?

    Leave a comment:


  • Danny3
    replied
    Oh, come on!
    WTF is with all the rush?
    Maybe the developer is sick, in a country with problems, has some personal things to solve.

    We have been waiting for this driver for years.
    Just leave it alone or maintain it yourself!

    Leave a comment:


  • markg85
    replied
    Originally posted by Shagga, Son of Dolf View Post
    This imho shows, why Microsofts apparent support for OSS is only hollow marketing for the masses and for maintaining an image, and has not led for any actions and changes outside some of their unimportant side projects which they don't rely on. At places where they could help Linux, which they claim to love, they rely on 3rd-parties to do their work for them (NTFS, exFAT) instead of contribuiting directly, and their "support" consists of nothing but not suing and not enforcing patents.
    You either haven't read it properly, just don't understand it or are willfully posting crap to cause a stir.

    Like others here too, i have no problem bashing microsoft.
    However... in this case this isn't their fault at all. Blame Paragon Software, not microsoft.

    Leave a comment:

Working...
X