Hi Clemens, all, Am 2013-09-17 20:53, schrieb Clemens Eisserer: > a. comment out the free()-calls which led to crashes
Uh, well, I did not want to go that far ;) I'm certainly not the greatest programmer around, but not freeing allocated memory seems kind of drastic. Anyway, I checked out a copy of btrfs-progs from git and took a look at the code. Then I remembered valgrind and instead of running btrfs restore on the broken machine I tried it on my images (saved with dd on an external hard drive). Running the self-compiled program using sudo resulted in the same errors. Now the (at least for me) fun part. Running it under my UID I managed to retrieve 13GB worth of data so far before hitting the same error: Error in `./btrfs': free(): invalid next size (normal) I would be glad for someone's opinion on this. Regards! -- j.hofmüller -- 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
