271–280 of 406 posts
No checksumming?
I have a theory on this regarding consumer devices: Checksumming drives a lot of support calls that would otherwise not happen. As long as the errors are in media files and not meta-data, most consumers are going to be oblivious to bit rot in their downloaded movies and photos. Enabling checksumming is going to reveal a lot of errors that would otherwise be silently ignored (spoken from experience running a ZFS media…
ReFS already does this when you're running it on non-redundant storage - integrity streams are only enabled on mirrored/parity configurations.
Earlier quoted context omitted.
Apple is far more willing to switch to more newer technologies than Microsoft is.
... and Microsoft is far more willing than Apple to put effort into backwards compatibility.
Lately, Microsoft is showing that they aren't afraid to break things in the name of progress. If W10 is indeed the last version of Windows, maybe that's okay.
Earlier quoted context omitted.
Yes. I was a heavy user of ZFS on Mac OS X back then. Was on the developer mailing list for that implentation, submitting bugs and talking to Apple developers working like mad to ship it. Then Steve Jobs' buddy Larry bought Sun, and licensing of ZFS became basically impossible to sort out on time. So they dropped it. Was that 2007 or 2009?
The Sun acquisition was announced in 2009 and closed in 2010. It may have been related, but I have my own suspicions about about what caused Apple to jettison their port.
Earlier quoted context omitted.
Apple is far more willing to switch to more newer technologies than Microsoft is.
... and Microsoft is far more willing than Apple to put effort into backwards compatibility.
Earlier quoted context omitted.
Many filesystems exist that do not run on a "plain" read/write block device, because storage based on flash is more complicated than the old random-sector-access magnetic hard drives. See for example UBIFS and JFFS2 on Linux. Having full and direct low-level control of on-board SSDs could very well be advantageous for performance and longevity of the flash on modern macbooks. Things like combining TRIM with low-level…
Taking advantage of the differences between flash and spinning rust only requires that you know which one you're running on. Moving the wear leveling code into the OS where the filesystem can see it is an interesting idea but why aren't we doing that for all SSDs and operating systems then?
No checksumming?
It would be unbelievable if they really didn't have checksumming. Could it just be that they haven't documented it yet? That seems weird and unlikely, but... not was weird and unlikely as APFS not having checksumming.
I hope finally a filesystem that allows me to unplug a USB drive (while it is still mounted) without potentially corrupting it.
Earlier quoted context omitted.
Checksumming makes no sense on modern hardware. Hard Drives and SSDs use CRCs already. When a sector goes bad on a hard drive, the firmware will mess about retrying and altering the analog amplifiers to try to get the signal back. If it gets the data back, it might "recover" by moving the data to spare sectors. Without a CRC, the firmware would have no way of differentiating between a sector read correctly and one th…
At least with bigger SATA disks I see regularly checksum errors on btrfs/ZFS and a rising bad sector count. The disk usually replaces the sectors on the next write but when reading it returns either zeros or wrong data. It's nice to know what files are affected from bad sectors. It's not common but common enough to have it.
If I see one bad sector develop on a disk for no obvious reason, it's getting replaced ASAP because it's a sign that more will follow very soon.