4 ms·

Discussion on reddit: https://www.reddit.com/r/linux/comments/i9mdqg/ntfs_readwrite_driver_gpl_implementation_by/ https://www.reddit.com/r/linux/comments/i9mdq

Discussion on reddit: https://www.reddit.com/r/linux/comments/i9mdqg/ntfs_readwrite_driver_gpl_implementation_by/ https://www.reddit.com/r/linux/comments/i9mdqg/ntfs_readwrit... When exFAT was announced about 5 months ago Paragon Software posted a rant against that. Rant is posted here: https://news.ycombinator.com/item?id=22688058 https://news.ycombinator.com/item?id=22688058

tomc1985 6y ago
Paragon, purveyors of fine commercial filesystem drivers that corrupt my hard drives? LOL
- Quekid5 6y ago
  I guess it's not that surprising really[0], but it is quite amusing in combination with the company name. [0] If you tie your company's worth to a proprietary technology.
- mehrdadn 6y ago
  It's easy to laugh at them but I've had corruptions from Linux's existing NTFS implementation too.
  - booi 6y ago
    Isn't Linux's existing NTFS implementation read-only? I'd be very surprised you would get corruptions from that..
    - SXX 6y ago
      FUSE one is not just read-only. It had capacity to do write on NTFS partitiona for decade at least.
      - brendawalsh 6y ago
        But, it is FUSE.
        bluejekyll 6y ago
        Am I correct in saying that there shouldn’t be any reason that being FUSE would in and of itself cause corruption? Performance is a different question, since it’s not in kernel.
        brongondwana 6y ago
        Off the top of my head... ordering violations. FUSE has a lot less control about the exact order in which things get written to disk, meaning that you are more likely to wind up with the wrong parts having committed down first if there's a crash.
      - booi 6y ago
        That’s FUSE which is in userspace. The kernel driver is read-only. I believe it never progressed past that due to licensing issues.
        SXX 6y ago
        I know what FUSE driver is, but my educated guess would be that almost no one ever used in-tree kernel-space driver which you referring to. So when people talking about issues with old driver that's almost certainly NTFS-3g
  - tomc1985 6y ago
    I've had issues with their Windows HFS+ driver too, shit wiped out a hard drive that I later learned wasn't fully backed up
    - mehrdada 6y ago
      +1 had the same issue with their HFS+ driver, and it did not take that long to encounter it.
- nailer 6y ago
  I mean the thread is they're open sourcing their work (if by commercial you mean proprietary).

tomc1985 6y ago

Paragon, purveyors of fine commercial filesystem drivers that corrupt my hard drives? LOL

Quekid5 6y ago
I guess it's not that surprising really[0], but it is quite amusing in combination with the company name. [0] If you tie your company's worth to a proprietary technology.
mehrdadn 6y ago
It's easy to laugh at them but I've had corruptions from Linux's existing NTFS implementation too.
- booi 6y ago
  Isn't Linux's existing NTFS implementation read-only? I'd be very surprised you would get corruptions from that..
  - SXX 6y ago
    FUSE one is not just read-only. It had capacity to do write on NTFS partitiona for decade at least.
    - brendawalsh 6y ago
      But, it is FUSE.
      - bluejekyll 6y ago
        Am I correct in saying that there shouldn’t be any reason that being FUSE would in and of itself cause corruption? Performance is a different question, since it’s not in kernel.
        brongondwana 6y ago
        Off the top of my head... ordering violations. FUSE has a lot less control about the exact order in which things get written to disk, meaning that you are more likely to wind up with the wrong parts having committed down first if there's a crash.
    - booi 6y ago
      That’s FUSE which is in userspace. The kernel driver is read-only. I believe it never progressed past that due to licensing issues.
      - SXX 6y ago
        I know what FUSE driver is, but my educated guess would be that almost no one ever used in-tree kernel-space driver which you referring to. So when people talking about issues with old driver that's almost certainly NTFS-3g
- tomc1985 6y ago
  I've had issues with their Windows HFS+ driver too, shit wiped out a hard drive that I later learned wasn't fully backed up
  - mehrdada 6y ago
    +1 had the same issue with their HFS+ driver, and it did not take that long to encounter it.
nailer 6y ago
I mean the thread is they're open sourcing their work (if by commercial you mean proprietary).