On Mon, Dec 28, 2015 at 3:55 PM, Waxhead <waxhead@xxxxxxxxx> wrote: > I tried the following.... > > btrfs-image -t4 -c9 /dev/sdb1 /btrfs_raid6.img > checksum verify failed on 28734324736 found C3E98F3B wanted EB2392C6 > checksum verify failed on 28734324736 found C3E98F3B wanted EB2392C6 > checksum verify failed on 28734324736 found 5F516E2A wanted BBB2D39C > checksum verify failed on 28734324736 found C4AA0B8D wanted 41745FB5 > checksum verify failed on 28734324736 found C3E98F3B wanted EB2392C6 > bytenr mismatch, want=28734324736, have=16273726433708437499 > Error reading metadata block > Error adding block -5 > checksum verify failed on 28734324736 found C3E98F3B wanted EB2392C6 > checksum verify failed on 28734324736 found C3E98F3B wanted EB2392C6 > checksum verify failed on 28734324736 found 5F516E2A wanted BBB2D39C > checksum verify failed on 28734324736 found C4AA0B8D wanted 41745FB5 > checksum verify failed on 28734324736 found C3E98F3B wanted EB2392C6 > bytenr mismatch, want=28734324736, have=16273726433708437499 > Error reading metadata block > Error flushing pending -5 > create failed (Success) > > Well, I can't make out what this is supposed to mean, but no output file... Dunno. Maybe btrfs-show-super -fa for each device, along with btrfs-debug-tree <dev> output to a file might have some useful info for a dev. It could be a while before we hear from one though, considering the season. > Here is a (rather long) stack trace... should I use a pastebin instead of > such large posts on this mailinglist?! Nah if it posts without wrapping and all of it can go on list, best on list. I'm expecting the balance fails because the fs is actually damaged in a way neither the kernel or btrfs check can work around. So I think it's an interesting case, but even better is if it's reproducible. The thing is, you have one device with generation 0 which really makes no sense to me; and another with generation 4 which is the one sabotaged. Yet the fs mounts without complaint, and without the need for degraded mount option. Seems strange to me, and may not be reproducible if there's something else that's happen unaccounted for. -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
