Am 26.01.2017 um 12:01 schrieb Oliver Freyermuth:
>Am 26.01.2017 um 11:00 schrieb Hugo Mills:
>> We can probably talk you through fixing this by hand with a decent
>> hex editor. I've done it before...
>>
> That would be nice! Is it fine via the mailing list?
> Potentially, the instructions could be helpful for future reference, and
> "real" IRC is not accessible from my current location.
>
> Do you have suggestions for a decent hexeditor for this job? Until now, I
> have been mainly using emacs,
> classic hexedit (http://rigaux.org/hexedit.html), or okteta (beware, it's
> graphical!), but of course these were made for a few MiB of files and are not
> so well suited for a block device.
>
> The first thing to do would then probably just be to jump to the offset where
> 0xd89500014da12000 is written (can I get that via inspect-internal, or do I
> have to search for it?), fix that to read
> 0x00a800014da12000
> (if I understood correctly) and then probably adapt a checksum?
>
My external backup via btrfs-restore is now done successfully, so I am ready
for anything you throw at me.
Since I was able to pull all data, though, it would mainly be something
educational (for me, and likely other list readers).
If you think that this manual procedure is not worth it, I can also just
scratch and recreate the FS.
Cheers,
Oliver
--
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
