At 03/01/2017 04:23 PM, Marc Joliet wrote:
On Tuesday 28 February 2017 23:14:54 Marc Joliet wrote:
I think I'm at that point now myself, unless anybody has any other ideas.
For example, could the --init-extent-tree option to btrfs-check help, given
that I needed to pass -w to btrfs-image?
--init-extent-tree should be avoided normally, unless you're 100% sure
about only extent tree is corrupted, and you have enough faith that
--init-extent-tree can finish.
Or it will mostly make things worse.
Before trying any RW btrfs check operations, did you run btrfs check on
the image?
And btrfs check --mode=lowmem is also recommended as in some rare case,
low mem mode can detect bug which original mode doesn't.
(And it also helps us to enhance lowmem mode)
Also, the image is complete, so I only need to find somewhere where I can
upload a 9.4 GB file.
Is it a compressed dump? Dumped with btrfs-image -c9?
If so, such large one won't help much unless there is some developer
really interested in inspecting the image.
Thanks,
Qu
Greetings
--
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
