On Thu, Nov 20, 2014 at 6:27 PM, Boris Chernov <aqs1...@hotmail.com> wrote:
> Since it failed after "checking extents" I decided to try > --init-extent-tree: There might be hope yet if you didn't use --repair which is said on the wiki and many times on this list is kindof a last resort. But at the very least before going with the hammer approach you should upgrade your btrfs-progs which is kind old. Current is 3.17.2. I suggest upgrading and just posting the results from 'btrfs check <device>' without any options and see what you get. This check and --repair code are mostly in btrfs-progs, whereas the mount time fixing code is in the kernel. So upgrading btrfs-progs may be sufficient for your case, but ultimately it might be necessary to go to a newer kernel also. > Btrfs v3.14.1 -- 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
