Thanks for the link, I'm glad to see that restore work for you. I've tried this also and everything doesn't work ending up with segfault.
Unfortunately in my case I had some important files on btrfs partition, due to performance reasons (it was on SSD). I doesn't find solution in mailing-list archives, because there are not so many cases in which tools refuses to work. So, now I'm trying to debug btrfs tools, aiming first to get btrfs-zero-log working. > > First answer (probably not too helpful, but gets the point across): > > Since btrfs is still not fully stable and you are urged to keep backups > if you value the data, then restore from them. If you don't have them, > by definition you obviously don't value the data enough to bother with > the hassle of backing it up, so no big deal if you lose it, right? > > Second answer (hopefully more helpful, but I'm obviously a bit grumpy > today; I could put off answering until I'm not so grumpy, but I know what > it's like to be waiting for an answer, so read thru the grumpy and we can > both hope the solution works): > > It used to be common courtesy to read a couple weeks of the the backgroup/ > backlist before posting questions as they might be answered already. I > guess it isn't so these days... > > Anyway, see the second half of the following post (the first half is a > different problem and solution) dealing with using restore with btrfs- > find-root and etc, along with the wiki link mentioned (and of course the > manpages as well). With some luck you can still get btrfs restore > working. It worked for me recently (as you can see there, I had backups > but they weren't as current as I would have liked). > > http://permalink.gmane.org/gmane.comp.file-systems.btrfs/37980 > -- 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
