4 ms·
Some updates, but it's still old. There is only so much you can do while still maintaining Microsoft's legendary backwards compatibility. For example I'm runni
by hu3 3y ago
Some updates, but it's still old. There is only so much you can do while still maintaining Microsoft's legendary backwards compatibility.
For example I'm running Windows 11 Pro on this machine with a brand new NVME.
"fsutil.exe fsinfo ntfsinfo c:" tells me [0] I'm running NTFS v3.1 which was released 22 years ago [1].
[0] https://i.imgur.com/VcXNO4P.png https://i.imgur.com/VcXNO4P.png
[1] https://en.wikipedia.org/wiki/NTFS https://en.wikipedia.org/wiki/NTFS
- thomastjeffery 3y ago> There is only so much you can do while still maintaining Microsoft's legendary backwards compatibility. ...like adding support for more filesystems. I'm curious about what (and when) other parts of the IO stack have been updated. Something has to have changed to add trim support: I'm guessing the scheduler.
- hu3 3y agoIndeed. It's impressive how they managed to extend it. Wikipedia provides some hints: > Although subsequent versions of Windows added new file system-related features, they did not change NTFS itself. For example, Windows Vista implemented NTFS symbolic links, Transactional NTFS, partition shrinking, and self-healing.[21] NTFS symbolic links are a new feature in the file system; all the others are new operating system features that make use of NTFS features already in place. If I had to guess, most of these new functionalities leverage NTFS metadata: https://ntfs.com/ntfs-system-files.htm https://ntfs.com/ntfs-system-files.htm