On Thu, Feb 4, 2021 at 4:04 AM [email protected] <[email protected]> wrote:
> https://susepaste.org/51166386 It's raid1 metadata on the same physical device, so depending on the device, if the metadata writes are concurrent they may end up being deduped by the drive firmware no matter that they're supposed to go to separate partitions. Feb 02 13:43:37 kimera.rozsas.eng.br kernel: BTRFS error (device sdc2): unable to fixup (regular) error at logical 557651984384 on dev /dev/sdc1 Feb 02 13:43:37 kimera.rozsas.eng.br kernel: BTRFS error (device sdc2): unable to fixup (regular) error at logical 557651869696 on dev /dev/sdc1 This suggests both copies are bad. > So, what is going here ? > How can I fix this FS ? I would do a memory test, the longer the better. Memory defects can be evasive. Take the opportunity to freshen backups while the file system still mounts read-only. And then also provide the output from btrfs check --readonly It might be something that can be repaired, but until you've isolated memory, any repair or new writes can end up with the same problem. But if it's not just a bit flip, and both copies are bad, then it's usually a case of backup, reformat, restore. Hence the backup needs to be the top priority; and checking the memory the second priority. -- Chris Murphy
