Hacker News new | ask | show | jobs
by wannacboatmovie 580 days ago
> If you have SSD->LUKS->GPT->LVM->Ext4, then a bug on any of the (newer, buggier) components before your journaled FS means you lost data

And yet it's never happened to me. Dozens upon dozens of systems. Linux or Windows or Mac for that matter.

I've toted around a laptop with whole disk encryption for > 15 years and never lost data. Not once. Even after a forced power off.

I have, however, lost data to major FS corruption on an OpenBSD system with no encryption whatsoever. More than once. Still using ancient MBR and legacy boot because, well, OpenBSD.

3 comments

> I've toted around a laptop with whole disk encryption for > 15 years and never lost data.

me too. Until I did. Negative anecdotes in a discussion about rare events are unhelpful.

My point is not that journaling is useless and should be dropped (I only use openBSD in things that are either readonly storage or virtualized on a host which does have proper FS). My point is that the "new setup" used by most distros introduced a lot of things that are above the journal. We have been rocking FDE for over 10yr, but the mass of people with crappy hardware and who just unplug their computers are only exposed to FDE for the past couple years.

My experience with LUKS robustness is less so, but I've uncleanly powered off many a laptop with BitLocker, FileVault, and commercial encryption with no ill effects.
> Still using ancient MBR and legacy boot because, well, OpenBSD.

All this does is tell me you're young for such a hostile tone towards recently dominant, mildly deprecated tech. It wasn't too long ago that UEFI didn't really work well. I did 3 BIOS to UEFI migrations in the last year or so, on Linux, FreeBSD and Windows, because those machines booted bios up to recently.

> Still using ancient MBR and legacy boot because, well, OpenBSD.

OpenBSD supports UEFI.