This is the command I used after unlocking the luks device in a rescue environment and confirming it not mounting further:

sudo btrfs rescue zero-log /dev/mapper/luksroot

After that, I could mount again and boot.

Here’s more info on the command, to verify advice is sound: https://manpages.debian.org/testing/btrfs-progs/btrfs-zero-log.8.en.html#zero

EDIT: For me it didn’t happen during an update, btw. You might still need the chroot approach to make the system bootable again.

I’ve had this exact error a couple of weeks ago. You have to clear the replay log (and lose potentially 30 seconds of disk writes). Let’s see if I can find exact instructions before the end of my commute.

I partially agree, but this language intentionally doesn’t try to change the way the user interacts with the language. Just unlocks another target for running on. A native target even. That’s just great, right?

Been using OsmAnd for years now, but I hear organic maps (or now CoMaps) mentioned way more often. What features does CoMaps have that OsmAnd lacks?

What explanation do people envision, after which they would both understand the mechanism of free will and are convinced it exists? That understanding just seems contradictory to me, so either it doesn’t exist or we can’t define it.

Haskell