On Thu, Oct 23, 2014 at 07:16:22PM -0400, Zygo Blaxell wrote: > I attempted to run btrfs check --repair, but it got stuck spinning > in what appeared to be an infinite loop. strace and ltrace revealed > nothing, and gdb wasn't particularly helpful, so I rebuilt btrfs with > debug symbols and tried again. > > Now I get this from btrfs check: > > Couldn't map the block 17716610236416 > No mapping for 17716610236416-17716610252800 > Couldn't map the block 17716610236416 > Check tree block failed, want=17716610236416, have=0 > read block failed check_tree_block > Couldn't read chunk root 'btrfs rescue chunk-recover -v' seems to have fixed this. It ran in total silence for 15 hours (apparently it really does read all 13TB of filesystem!), then it asked a 141,000-line question about repairing three bad chunk tree segments. Good thing I was logging the terminal output. :-) Now I'm back to btrfs (3.17) check on this filesystem, so we'll see how that goes.
Attachment:
signature.asc
Description: Digital signature
