Hello Jogi, I'm not sure what's causing the free error, I'll keep looking. Have you tried running restore on your home subvolume yet? By default restore only works on the default subvolume which in your case is / The following command will try to restore your /home subvolume btrfs restore -i -r 258 [image] [destination] Run that and see if you get your home folder restored. Hopefully the errors are only on the root volume. You can also try the /var subvolume which is 257 instead of 258. Let me know if any of that helps, Frank On Wed, Sep 18, 2013 at 2:15 PM, Jogi Hofmüller <jogi@xxxxxx> wrote: > 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 majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- 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
