3 ms·

Why would someone do that? NTFS is stable, faster than btrfs and has all the same features.

by rurban 2y ago

rnd0 2y ago
The only reason I can think of is so that they can use the same FS in both windows and linux -but with ntfs, they already can. Mind you, with openzfs (https://openzfsonwindows.org/ https://openzfsonwindows.org/) you get windows (flakey), freebsd, netbsd and linux but -as I said; I'm not sure zfs is super reliable on windows at this point. Mind you, I just stick with ntfs -linux can see it, windows can see it and if there's extra features btrfs provides they're not ones I am missing.
- mistaken 2y ago
  With ntfs you have to create a separate partition though. With btrfs you could create a subvolume and just have one big partition for both linux and windows.
- ComputerGuru 2y ago
  I’m a die-hard ZFS fan and heavy user since the Solaris days (and counting) but I believe the WinBtrfs project is in better (more useable) shape than the OpenZFS for Windows project.
paines 2y ago
what ?!?! NTFS has no case sensitivity no compression. And I guess a couple of more things I do not want to miss.
- rurban 2y ago
  NTFS does have case-sensitivity, just nobody dares to activate it. Compression is big, but I thought I've read winbtrfs neither
  - inetknght 2y ago
    I activated it back in mid 2010 or so. I had the most amazing pikachuface when random things stopped working because it could no longer find that file it wanted to load with an all-lowercase-string even though the project builds it with CapitalCase. Sigh...
- cesarb 2y ago
  > what ?!?! NTFS has no case sensitivity no compression. As the sibling comment mentioned, NTFS does have a case-sensitive mode, for instance for the POSIX subsystem (which no longer exists, but it existed back when NTFS was new); I think it's also used for WSL1. And NTFS does have per-file compression, I've used it myself back in the early 2000s (as it was a good way to free a bit of space on the small disks from back then); there was even a setting you could enable on Windows Explorer which made compressed files in its listing blue-colored.
- ComputerGuru 2y ago
  NTFS has per-folder case sensitivity flag. You could set it online at anytime prior to Windows 11, but as of 11 you can now only change it on an empty folder (probably due to latent bugs they didn’t want to fix). NTFS had mediocre compression support from the very start that could be enabled on a volume or directory basis, but gained modern LZ-based compression (that could be extended to whatever algorithm you wanted) in Windows 10, but it’s unfortunately a per-file process that must be done post-write.
WhyNotHugo 2y ago
For fun? To prove that it is possible? As a learning activity? There are millions of reasons to write software other than "faster" or "more features". I can imagine this being convenient (albeit risky) when migrating Windows to Linux if you really can't afford a spare disk to backup all your data.

Why would someone do that? NTFS is stable, faster than btrfs and has all the same features.

by rurban 2y ago

Why would someone do that? NTFS is stable, faster than btrfs and has all the same features.

rnd0 2y ago

The only reason I can think of is so that they can use the same FS in both windows and linux -but with ntfs, they already can. Mind you, with openzfs (https://openzfsonwindows.org/ https://openzfsonwindows.org/) you get windows (flakey), freebsd, netbsd and linux but -as I said; I'm not sure zfs is super reliable on windows at this point. Mind you, I just stick with ntfs -linux can see it, windows can see it and if there's extra features btrfs provides they're not ones I am missing.

mistaken 2y ago
With ntfs you have to create a separate partition though. With btrfs you could create a subvolume and just have one big partition for both linux and windows.
ComputerGuru 2y ago
I’m a die-hard ZFS fan and heavy user since the Solaris days (and counting) but I believe the WinBtrfs project is in better (more useable) shape than the OpenZFS for Windows project.

paines 2y ago

what ?!?! NTFS has no case sensitivity no compression. And I guess a couple of more things I do not want to miss.

rurban 2y ago
NTFS does have case-sensitivity, just nobody dares to activate it. Compression is big, but I thought I've read winbtrfs neither
- inetknght 2y ago
  I activated it back in mid 2010 or so. I had the most amazing pikachuface when random things stopped working because it could no longer find that file it wanted to load with an all-lowercase-string even though the project builds it with CapitalCase. Sigh...
cesarb 2y ago
> what ?!?! NTFS has no case sensitivity no compression. As the sibling comment mentioned, NTFS does have a case-sensitive mode, for instance for the POSIX subsystem (which no longer exists, but it existed back when NTFS was new); I think it's also used for WSL1. And NTFS does have per-file compression, I've used it myself back in the early 2000s (as it was a good way to free a bit of space on the small disks from back then); there was even a setting you could enable on Windows Explorer which made compressed files in its listing blue-colored.
ComputerGuru 2y ago
NTFS has per-folder case sensitivity flag. You could set it online at anytime prior to Windows 11, but as of 11 you can now only change it on an empty folder (probably due to latent bugs they didn’t want to fix). NTFS had mediocre compression support from the very start that could be enabled on a volume or directory basis, but gained modern LZ-based compression (that could be extended to whatever algorithm you wanted) in Windows 10, but it’s unfortunately a per-file process that must be done post-write.

WhyNotHugo 2y ago

For fun? To prove that it is possible? As a learning activity? There are millions of reasons to write software other than "faster" or "more features". I can imagine this being convenient (albeit risky) when migrating Windows to Linux if you really can't afford a spare disk to backup all your data.