Journaling filesystems have been around for decades now; I don't think I've had a data loss incident since I stopped using Windows 98? I know it's volunteer driven but it seems like working on data integrity might be more of a benefit for security than some of the gimmicks like TRAPSLED.
OpenBSD had Soft Updates, which isn't really journaling but sort of similar. It was suppose to help with with file system integrity, in the case of crashes. OpenBSD removed it last year because it got in the way of VFS updates, and was hard for the team to maintain[1].
I love OpenBSD, but it really does need a modern filesystem. The current team might be to small or just not have the right people to do a new filesystem. HammerFS2 could maybe be ported (and one has to wonder if that's not one of the thing that would requires VFS layer updates). Much of the current work on filesystems are being poured into GPL licensed code or ZFS, which also have an unfortunate license, so OpenBSD either has to borrow HammerFS, or do their own thing, which they probably don't have the resources for.
BSDs bet on permissive license hoping companies would drop code on them. Turned out companies were either using linux or dumping abandoned code as GPL to strategically keep out of competitors.
BSD licenses were a thing before GPL lost the final battle, when linus accepted the tainted-kernel compromise. Now it's a relic of a bygone time, which show allegiance to a side on a war that no longer matters.
> I don't think I've had a data loss incident since I stopped using Windows 98?
Data loss from a kernel crash or power loss, sure, have not seen that in some time.
However data loss from disk failure is something I've seen in the current century. I started using ZFS in my home network when I began to see that at home. I haven't had anything major that ZFS with redundancy couldn't recover since.
The journal does what it's supposed to, doesn't it? I.e: keep the file system from breaking on panics, or power loss. Sure it doesn't protect you against a corruption bug in LVM et al., but that doesn't make it useless.
Yes, if you search for people trying to mount a LUKS volume image readonly to then try (somewhat successfully in my case) to get data from the journal or run destructive fsck operations, you will find lots and lots of examples.
> 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.
> 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.
You joined a discussion inside the discussion that was about Mexico firing missiles at the US. If you don't want to discuss similarities of both scenarios, don't join the discussion.
And, hence, we should give them all the arms and tools they need and the freedom to use them to end it quickly. The dithering on behalf of Biden and Scholz is what's prolonging this.
Given that Russia is invading them and that they are showing no reluctance to stand up to them, yes? Arm them, give them everything they need without restriction and Russia will be sent home to their borders, bloodied and cowed.
That would only work if the C code was treated as a generated artifact and not touched directly. If the C code is worked on directly it will be just as susceptible to unsafe changes as before.
A regulatory body that is staffed by people who are well versed in the intracacies of the industries they are overseeing, rather than Representative Marge McCrazyPants who legitimately believes in the existence of space lasers owned and operated by certain religious adherents.
reply