On Nov 3, 2014, at 12:48 PM, Florian Lindner <mailinglists@xxxxxx> wrote: > > Ok, problem is that I need to organise another hard disk for that. ;-) > > I tried restore for a test run, it gave a lot of messages about wrong > compression length. I found some discussion about that, but I don't know if > its indicates an actual error or not? I did use compression on the drive. This is btrfs-progs 3.17? I know there were compression problems with kernel code but that was fixed in 3.16. I can't tell you why it happens on 3.17 or whether it's a bogus error. > Is there some guarantee that the data restore restores are correct or is it > just a I try what I can do… No guarantee as far as I know, it's file scraping. There is a recent email from Duncan on this topic about two ways to do restore and he was doing both to make sure he got everything. I vaguely recall things like links aren't restored. Files themselves should be. There's a wiki entry on how to use restore that's worth looking at. In conjunction with btrfs-debug-tree -R you should be able to find a state where you can restore important files. 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
