Re:Linux: Ext4 data corruption in 6.1.64-1
by mustache_kimono on Sunday December 10, 2023 @04:06PM
(#38595062)
I'm trying to understand what exactly this is testing/demonstrating.
Like: "Wow, but why should I care?" I'm not sure being able to fsck a random disk image shows resiliency.
Re:Linux: Ext4 data corruption in 6.1.64-1
by grrandalf on Monday December 11, 2023 @05:05PM
(#38606144)
(not the author) The metadata is a contiguous range of disk blocks. I think the intuition is that such layouts are likely to require simpler filesystem code to manipulate. [versus (iirc) ZFS which may have metadata blocks scattered throughout the disk, probably requiring more intricate code to keep track of].
Re:Linux: Ext4 data corruption in 6.1.64-1
by mustache_kimono on Tuesday December 12, 2023 @03:55PM
(#38618376)
> [versus (iirc) ZFS which may have metadata blocks scattered throughout the disk, probably requiring more intricate code to keep track of].
So -- you think redundant metadata is a bad thing? Try wiping your metadata and then trying to fsck that random disk image.
Again, has this been the source of data corruption you're aware of? This seems like a "Maybe, it could be this way, but I don't know" kind of take.
Re:Linux: Ext4 data corruption in 6.1.64-1
by 1000thVisitor on Sunday December 10, 2023 @05:12PM
(#38595607)
> To give you an example, fsck.ext4 will happily carve a working filesystem out of random data
What application does this have for recovering user data? Would it not be more interesting to see how much of the user data can be recovered? Or are you implying that the random data can symbolize the user data here and much of it would be recovered?
Combine ext4's dumb but robust approach to journaling and robust metadata layout (for example inodes are statically allocated) with fsck.ext4 (which got refined for years) and you can recover from any situation.
To give you an example, fsck.ext4 will happily carve a working filesystem out of random data, as long as there is a valid superblock. Seriously - try it yourself: