News for hackers. Stuff that matters.
Re:Linux: Ext4 data corruption in 6.1.64-1 by userbinator on Sunday December 10, 2023 @02:34AM (#38589843)
I think "corruption you can recover from" seems far too vague; you can recover from any corruption with backups.
Re:Linux: Ext4 data corruption in 6.1.64-1 by viraptor on Sunday December 10, 2023 @03:21AM (#38590042)
If you're trying to be padantic and missing forest for the trees... Sure.
Re:Linux: Ext4 data corruption in 6.1.64-1 by piperswe on Sunday December 10, 2023 @02:48AM (#38589905)
The way I'd interpret it is that it's non-serious if fsck can repair it. Not sure if that's accurate though, just the way it sounds to me.
Re:Linux: Ext4 data corruption in 6.1.64-1 by LoganDark on Sunday December 10, 2023 @10:16AM (#38592052)
Sure, and you can recover from any hardware failure with a separate computer. In fact, you can recover from death simply by cloning yourself. What's the issue?

The issue is that some people don't have the time, money, and/or willpower to invest in backups. Some people only have one volume, or one copy of each volume at least, and need to recover their data using only that one volume if something gets corrupted. That's what "corruption you can recover from" means. Using a backup is not recovering from corruption; it's replacing the corruption with the pre-corrupted data. Recovering from corruption involves actually transforming the corrupted data back into non-corrupted data.

Re:Linux: Ext4 data corruption in 6.1.64-1 by remram on Sunday December 10, 2023 @11:20AM (#38592580)
I think you're agreeing with userbinator here.
Re:Linux: Ext4 data corruption in 6.1.64-1 by LoganDark on Sunday December 10, 2023 @11:32AM (#38592695)
Not really. They're arguing that backups count as recovering from corruption, where my argument is that backups don't count because the only thing you're doing is discarding the corruption, not recovering from it.
Re:Linux: Ext4 data corruption in 6.1.64-1 by tremon on Sunday December 10, 2023 @04:34PM (#38595273)
In this case, I would say that backups are not relevant protection. In order to restore something from backup, you would first need to know that a restore from backup is needed, and secondly you need to know what the last-known good copy is.

This is a silent data corruption bug (data is written at the wrong offset, IIUC) with no known method to detect the error condition except to compare the resulting data with a known-good copy. The next backup run will happily accept the corrupted file contents into the backup vault, and unless someone happens to stumble upon the corrupted data, the last-known good copy will eventually be rotated out.