4 ms·
Not much honestly, NTFS is known for corrupting data over a long enough timeline (so it isn't suitable for server storage).
by phendrenad2 5y ago
Not much honestly, NTFS is known for corrupting data over a long enough timeline (so it isn't suitable for server storage).
- dataflow 5y ago> NTFS is known for corrupting data over a long enough timeline Any links?
- phendrenad2 5y agoApparently it's called "bit rot": https://www.reddit.com/r/DataHoarder/comments/67h28o/bit_rot_detection_and_correction_on_windows/ https://www.reddit.com/r/DataHoarder/comments/67h28o/bit_rot...
- dataflow 5y agoBit rot has nothing to do with NTFS though? It's a general hardware degradation issue. (Where does that say it's NTFS-related?)
- deleted 5y ago[deleted]
- timbit42 5y agoThere are filesystems (eg. ZFS, BtrFS) which can detect and recover from hardware degradation. NTFS cannot, therefore the problem is NTFS-related, although not limited to NTFS.
- dataflow 5y agoIf that's what is meant, it's sure as heck misleading to single out NTFS with "known for corrupting data" as if it's somehow unique in not having error correction compared to ext4 or whatever.
- snvzz 5y agoError detection can be done in the layer underneath, including doing so within device mapper. A filesystem not doing its own vs a filesystem "corrupting data" are very different concepts.
- sigzero 5y agoI have never heard that before.
- technion 5y agoAny business anywhere running Windows file servers is running NTFS for server storage. Any business running a Hyper-V virtualisation, including large cluster, is running their virtual disks on NTFS. There's an irony here in Microsoft's next generation file system being "ReFS", with "resiliant" literally there in the name. And it has such a history of bugs and unimplemented features it's not safe for use outside of specific scenarios. Edit: the link phendrenad2 posted has a comment about a "server destroying bug" in ReFS.
- mgerdts 5y agoThat thread [1] is 4 years old. Is there recent credible evidence of ReFS being problematic? 1. https://www.reddit.com/r/DataHoarder/comments/67h28o/bit_rot_detection_and_correction_on_windows/ https://www.reddit.com/r/DataHoarder/comments/67h28o/bit_rot...
- technion 5y agoMicrosoft's documentation still refers to recommending NTFS "for general use" and then list specific places it's designed for. Also listed features still not available often make it a show stopper: https://docs.microsoft.com/en-us/windows-server/storage/refs/refs-overview https://docs.microsoft.com/en-us/windows-server/storage/refs... Most Hyper-V admins will be familiar with this thread which is still completely accurate. This is relevant as it's "by design" and won't change or be fixed. https://community.spiceworks.com/topic/2286588-please-do-not-use-refs-for-cluster-shared-volumes-provided-by-a-san https://community.spiceworks.com/topic/2286588-please-do-not... Here's a Veeam thread from 2019 talking about ongoing bugs: https://forums.veeam.com/veeam-backup-replication-f2/windows-2019-large-refs-and-deletes-t57726.html https://forums.veeam.com/veeam-backup-replication-f2/windows...