Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

btrfs send will fail when a single replica has bad metadata #864

Open
csnover opened this issue Aug 6, 2024 · 0 comments
Open

btrfs send will fail when a single replica has bad metadata #864

csnover opened this issue Aug 6, 2024 · 0 comments
Labels

Comments

@csnover
Copy link
Contributor

csnover commented Aug 6, 2024

I reported this on the mailing list and also discussed on IRC. I don’t see any mention of a fix in release changelogs since 6.6.3, and since not being able to pull snapshots off a degraded but functioning filesystem seems potentially catastrophic and initially prevented emergency backup of snapshots, I am opening this ticket.

Here, btrfs send used metadata from the damaged device and failed without trying the metadata from the healthy device:

BTRFS critical (device dm-0): corrupted leaf, root=1348 block=364876496896 owner mismatch, have 7 expect [256, 18446744073709551360]

The filesystem driver read from the healthy mirror and corrected the error. After btrfs scrub fixed all errors on the failing device, btrfs send worked.

btrfs-progs 6.6.3-1.2+b1
Linux kernel 6.9.10
Debian testing/sid

Best regards,

@kdave kdave added the bug label Aug 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants