"'"This removes the old ntfs driver. The new ntfs3 driver is a full replacement that was merged over two years ago. We've went through various userspace and either they use ntfs3 or they use the fuse version of ntfs and thus build neither ntfs nor ntfs3. I think that's a clear sign that we should risk removing the legacy ntfs driver."'"
First time poking around with Dev Drives, so doing a little performance testing by measuring dotnet build after git clean -xdf for @xunit (main branch).
On NVMe (NTFS): 17.5s
On SATA (NTFS): 17.9s
On VHDX (ReFS): 14.4s
On VHDX (ext4): 11.7s
The top 3 are built in Windows, and the bottom 1 is built in WSL 2 (Ubuntu 22.04). I wanted to be able to compare the two VHDX options.
Looks like Dev Drive is a win, but not as big as moving to Linux & ext4.
@pedrolamas It would also be important to me to know that it didn't make things (significantly) worse when not running on a DevDrive (for example, when running in CI).
Ok, I need your help.
While moving a folder on one of my nvmes, I suddenly get a Input/Output error. I already checked SMART - the SSD is totally fine. Of course I have no current backup of this exact folder 🙄 .
FS is NTFS (Yeah Ik it is shit) and I already tried ntfsfix...
Any ideas?
In which I demonstrate why using #exFAT for a sample content drive is a bad idea.
Though this demo specifically references #Mac and #APFS, on #windows I highly recommend following this maxim as well, and using #NTFS for your samples.
Please avoid #exFAT for samples wherever possible.
So a friend was asking me why she couldn’t copy some files from her MacBook to an external hard drive. Explaining the drive was formatted as #NTFS didn’t help but I think I got through to her with this reply and I stand by it! #MacOS