On 17/12/2010, at 00.18, Michael Niederle wrote: > Hi! > > Last week I crashed a btrfs file system. I didn't lose a lot of data because I > had current backups of most data and a full backup from a month ago. > > But I thought it would be a nice idea to have a rescue tool! Currently I have a > first release of this tool (surely buggy and runnning on little endian > architectures only). > Thank you for writing this tool. It was able to save some 80% of all data from a very broken btrfs filesystem. I could mount the filesystem but it would hang after just a few accesses with thousands of parent transid verify failed messages and btrfsck just exited immediately with some huge negative number as the only indication of what was wrong. Using the btrfsck -s $number option also didn't help but your tool seemed to do the job just fine. I still have the broken filesystem as I'm interested to see what Chris Masons new btrfsck code can do with it so if anybody is interested in further debugging I can probably help with that. Regards, Bryan Østergaard -- 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
