On 02/24/2017 12:47 AM, Lukas Tribus wrote: > Hello Hans, > > > Am 22.02.2017 um 20:40 schrieb Hans van Kranenburg: >> >> Question here is... is it easier for you to nuke the filesystem and >> restore the files from somewhere else, or do you want to figure out >> manually if it's recoverable, and spend some time with dd, hexedit, >> reading struct definitions in btrfs kernel C code etc... >> >> If the regular --repair can't fix it (and it can't do magic if you shoot >> a hole in it with a shotgun), then there's no automated other tool that >> can do it now. >> >> Since it's block 5242107641856 all the time, it might be worthwhile to >> have a look at it. Either it's that block, or there's a bigger mess >> hidden behind it. >> > > Thanks for all the inputs here and on IRC. I now have a good > understanding of what can > and what cannot be done realistically. > > The files are still fully readable and I'm going to backup as much data > as I can over the > next few days. > > Once that is done, I would like to go over the "btrfs recovery" thread > and see if it can > be applied for my case as well. I will certainly need your help when > that time comes... We can take a stab at it. -- Hans van Kranenburg -- 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
