I have no particular desire to use it. I just tried everything else first and thought it was worth a shot. If you think that version would help, can you point me to the git repo? The one I grabbed was git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git. On Mon, Jun 23, 2014 at 10:20 PM, Wang Shilong <wangsl.fnst@xxxxxxxxxxxxxx> wrote: > On 06/24/2014 09:17 AM, Chris Murphy wrote: >> >> On Jun 23, 2014, at 4:18 PM, Mike Hartman <mike@xxxxxxxxxxxxxxxxxxxx> >> wrote: >> >>> Can anyone offer any suggestions? Is this data really unrecoverable? I >>> have no idea what could have gone so severely wrong. >> >> "btrfs check --repair /media/mint/usb_data/sda6_check.img >> "btrfs check --repair --init-csum-tree --init-extent-tree >> /media/mint/usb_data/sda6_check.img > > My two cents:-) > > If you really want to use btrfs check --init-csum-tree --init-extent-tree, > i'd suggest you use > David Latest btrfs-progs branch which includes some latest bug fixes. > >> >> I think these things are going too far on actual file system without >> guidance, so it's superb you imaged the original drive first. Too many >> people get aggressive writing to the actual drive without backup images. You >> have both a dd image as well as btrfs-image which is really great. Hopefully >> someone can help find out what happened, it seems abruptly catastrophic, but >> also mixes messages where some information is being found but this one: >> * read block failed check_tree_block >> makes me think of partial media failure. It would be damn bad luck if your >> metadata is set to DUP, yet both copies are toast. Is this an HDD or SSD? >> >> Can you post the result from smartctl -x /dev/sdX #for the disk in >> question, maybe from a live system? >> >> >> 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 >> > -- 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
