4 ms·
"Causes non-serious data loss". What does that mean. Only affects cat videos?
by Animats 3y ago
"Causes non-serious data loss". What does that mean. Only affects cat videos?
- minikomi 3y agoYou lose your data but, like, it's just a prank man.
- pestatije 3y agoyeah, practical joke for using Linux...have a laugh and deal with it
- viraptor 3y agoI believe the Debian policy for reports says that for corruption you can recover from. Serious data loss would be losing your metadata and not being able to figure out where any of the files are, or corrupting all copies of the disk encryption key.
- userbinator 3y agoI think "corruption you can recover from" seems far too vague; you can recover from any corruption with backups.
- piperswe 3y agoThe 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.
- viraptor 3y agoIf you're trying to be padantic and missing forest for the trees... Sure.
- LoganDark 3y agoSure, 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.
- remram 3y agoI think you're agreeing with userbinator here.
- LoganDark 3y agoNot 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. You're basically throwing the corruption out and getting your data back from somewhere else. So you recover your data, but not from the corruption. You recover it from a backup. Similar, but not the same thing.
- tremon 3y agoIn 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.
- Grimburger 3y agoMost data is recoverable albeit slow to do. It takes some very bad conditions or intentional actions to make data recovery impossible. Current high level standards for military/diplomatic data sanatisation are complete physical destruction of hard disks. Even linux tools like shred have given up saying they can actually delete data from disks due to how SSD's work these days.
- eh8 3y ago> Even linux tools like shred have given up saying they can actually delete data from disks due to how SSD's work these days. Which emphasizes the importance of enabling full disk encryption immediately whenever you start using a new device--BitLocker if you're on Windows, FileVault on macOS, LUKS on Linux, etc. Trying to decrypt data is much harder than reconstructing deleted data on a stolen drive.
- Grimburger 3y agoTrue, properly zeroing out the headers on an encrypted drive will make recovery impossible. How to do that reliably is another question.
- WirelessGigabit 3y agoYou cannot with normal tools as writing a 0 to the SSD does not guarantee it overwrites the 0 you want. At best it does, at worst it writes the 0 somewhere else and remaps the bit (or whatever its physical storage thing is).
- WirelessGigabit 3y agoThis is especially a problem on macOS: https://support.apple.com/guide/disk-utility/erase-and-reformat-a-storage-device-dskutl14079/mac https://support.apple.com/guide/disk-utility/erase-and-refor... > Note: With a solid-state drive (SSD), secure erase options are not available in Disk Utility. For more security, consider turning on FileVault encryption when you start using your SSD drive. So if you set up a Mac without FileVault you can never erase everything. At least with my Lenovo I can do the secure erase.
- jbverschoor 3y agoSo you’re a dog person?
- AnAaaaardvark 3y agoI thought we all were dog people. Woof.
- sedatk 3y agoReminds me of this exchange from Coupling (UK): “How is it not serious if she died from it?” “She made an unsuccessful recovery”
- riffraff 3y agoFunny, I also thought of Coupling, except I was thinking of - how badly can you phrase yes? [Cuts to other scene] - No Such a good show.
- tremon 3y agoI think they meant non-catastrophic (no pun intended). From what I can tell, individual files can get corrupted when opened with O_DIRECT, but the filesystem structure will never fail. From the link in https://news.ycombinator.com/item?id=38591444 https://news.ycombinator.com/item?id=38591444 : > file position is not updated after direct IO write and thus [we] direct IO writes are ending in wrong locations effectively corrupting data. This may be a major problem for hypervisors using ext4-backed disk images. It wouldn't surprise me if qemu opens image files with O_DIRECT by default, but it would surprise me if professional shops were using ext4 as the backing store rather than a provisioning abstraction layer like dm_thin. Still, anyone using kvm on top of ext4 must not be having a good day.