BTRFS as default filesystem was a bad idea

[glb (Gregory Lee Bartholomew)]

@soconfused

[On single drive installations] metadata is in DUP mode, meaning there’s metadata duplicate to self-heal, but data is in single mode. Metadata corruption will self-heal.

In most cases the metadata should be able to self-heal, but not always. There have been cases where a failing SSD managed to corrupt both copies of the metadata.

Excerpts from another thread:

@chrismurphy

Can you provide the output from - check it for filenames/privacy.

btrfs insp dump-t -b 635198930944 /dev/nvme1n1p3

Both copies of this node or leaf are damaged is what the error is telling me. And they are damaged in different ways so … I think SSD is failing.

@koltpenny

I think it is:

btrfs-progs v6.14
checksum verify failed on 635198930944 wanted 0xd02a2bee found 0xf1a04115
checksum verify failed on 635198930944 wanted 0xd02a2bee found 0x793dc680
ERROR: failed to read tree block 635198930944

If you want your live data protected from a drive failure, you really need redundant drives. Backups are good as well, but if you have to rely on backups, you will inevitably lose data between whenever your last backup was made and when your drive failed.