On 03/24/2016 04:48 PM, Chris Murphy wrote:
It depends on the use case. On ARM it's common to depend on SD cards, and Btrfs will never pass corrupt data to user space. Corrupt user data is a kind of data loss, not good. But corrupt system files can lead to crashes and more corruption of both system files and user data. So, really not good.
The InfoSec concept of "Integrity" revolves around 'correctness'. Yes, obviously a file that has been mis-written, whatever the cause, is digital gobbledygook. Perhaps the checksum don't make sense; though that might be used to correct the data. Pinholes in the rust. Whatever. But there are other forms of a failure of Integrity. There's a whole class of 'finger problems' that corrupt the data without corrupting its digital integrity. The best recording mechanism in the world can't do anything about that. its an "Oh my ${DEITY}! I've just overwritten the annual report with my resignation letter!". or perhaps not that catastrophic. Maybe you changed your mind about something you wrote and the "undo' only undoes this edit session, what you want is the version you wrote the day before yesterday. And this isn't VMS. Its not that humans are fallible - well they are, but that's not my point. its that they are fickle and changeable. That's why I think snapshotting of user space is important. Its a human factor issue not a technical issue. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org