On Wed, Sep 21, 2016 at 9:24 AM, Jeffrey Michels <jeffr...@skyward.com> wrote: > Hello, > > I've booted into the latest nightly build of Fedora and run btrfs rescue > super-recover -v and also btrfs check. > > Super-recover reports that "All supers are valid, no need to recover." Btrfs > check displays the same errors as before: > > Parent trasid verified failed on xxxx wanted xxxx found xxxxx > Ignoring transid failure > Leaf parent key incorrect xxxxxxx > Bad block xxxxxxxxxxx > Errors found in extend allocation tree or chunk allocation. > > The check eventually fails with Segmentation fault (core dumped.) > > Attempting to mount with -o recovery results in the error "Can't read > superblock." I am able to mount the filesystem read-only however attempting > to copy all of the data off has been unsuccessful. It appears to hit a bad > area and just hangs. > > Is there anything else I can try?
Kinda weird that the supers are all valid with one tool but then the kernel says it can't read the superblock? Try btrfs-image -c9 -t4 and optionally with -s, and if the resulting file isn't too big put it somewhere and I can try to iterate some options on the file. You could do the same thing by imaging it, restoring the image to an LVM LV of the same size or bigger, and then see if there's a combination of btrfs check --repair; btrfs check --repair --init-extent-tree btrfs rescue chunk-recover btrfs rescue zero-log That or some other order of things might fix it, and the only way to know is to try it. And unfortunately each thing can make changes that can cause the next thing to fail. Hence doing this on an image. -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html