When a Btrfs Subvolume Crashes After an Unexpected Reboot
A sudden power loss or kernel panic can leave a Btrfs filesystem looking fine on the surface while hiding corruption inside a subvolume. The root of the issue is that Btrfs’ copy‑on‑write guarantees only hold if the metadata journal gets flushed. If the machine dies before that flush, the subvolume can become inconsistent and btrfs check will start complaining. The silver lining is that Btrfs ships with a handful of tools that, when used the right way, can recover most of the data. Below is a practical walk‑through that covers: