Re:What’s New in Apple Filesystems [pdf]
by Hackbraten on Tuesday June 11, 2019 @02:00PM
(#20157851)
I’m thinking of moving back from ZFS to APFS if I had such a workaround. Block- or file-level integrity is now the only thing that keeps me back.
[ Parent
| on HN ]
Re:What’s New in Apple Filesystems [pdf]
by privateSFacct on Tuesday June 11, 2019 @02:45PM
(#20158300)
What are the use cases folks have with super high reliability needs?
I'm generally more worried about an SSD falling over entirely - so focus is on duplication (raid with hot spare -> offsite S3 backup).
From a user perspective it's effectively a zero cost feature. Apple should add it in.
Re:What’s New in Apple Filesystems [pdf]
by privateSFacct on Tuesday June 11, 2019 @06:47PM
(#20160198)
OK - so they do a block level checksum (no error correction but it would let you know that something went wrong). Now something goes wrong with checksum. Is this a "zero cost" feature to have every app updated to handle this checksum error. What is gained? If you need reliability do something like SSD or a raid option and a backup.
The apps don't have to deal with it. It's a read error. Presumably something they already deal with. There's no operational difference for the end user between a block that can't be read and a block than can be read but with corrupted data. And yes, storage would ideally be paired with another physical device to provide redundancy and a mechanism to correct the error on the erroring device.
Or just pair it with iCloud and "cloud heal" the corrupted local data. Then mark the sector as bad and enjoy longer lifetime for the device.