On 11/25/2015 02:25 AM, Christoph Anton Mitterer wrote:
On Tue, 2015-11-24 at 13:35 +0800, Qu Wenruo wrote:
Hopes you didn't wait too long.
No worries, didn't hold my breath ;)
The fixing patch is CCed to you, or you can get it from patchwork:
https://patchwork.kernel.org/patch/7687611/
Unfortunately that doesn't make the error messages go away.
:(
Shall I start debugging again?
That's too bad...
Although you can try debugging again, but the result may not change at
all. :(
There maybe some complicated debugging method, like add breakpoint at
add_extent_rec() for special bytenr(bytenr in btrfsck error output, e.g
5993525264384) to check if its metadata flag is set correctly.
If metadata flag is not set correctly, the backtrace will provide a lot
of useful info...
But that's what dev should do, not an end user.
I'm totally OK if you can't provide that output.
I'll continue searching the code for any possible false alert.
But without a local test image, I'm afraid you may try several patches
until a final fix is found....
Thanks,
Qu
Cheers,
Chris.
--
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
