Mordechay Kaganer wrote on 2015/11/18 07:18 +0200:
B.H.
On Wed, Nov 18, 2015 at 5:02 AM, Qu Wenruo <quwenruo.btrfs@xxxxxxx> wrote:
在 2015年11月17日 13:12, Mordechay Kaganer 写道:
B.H.
[ 836.026606] BTRFS warning (device md1): block group 12969790406656
has wrong amount of free space
[ 836.026610] BTRFS warning (device md1): failed to load free space
cache for block group 12969790406656, rebuild it now
[ 1033.619798] BTRFS warning (device md1): block group 15322358743040
has wrong amount of free space
[ 1033.619801] BTRFS warning (device md1): failed to load free space
cache for block group 15322358743040, rebuild it now
Block group seems to be corrupted, maybe some other place in extent tree is
also corrupted.
Personally speaking, this would not be a huge problem and can be fix by
btrfsck --init-extent-tree --repair to fix it.
Thanks. That's what i get so far (it takes several hours to complete
because the partition is huge):
# btrfsck --init-extent-tree --repair /dev/md1
enabling repair mode
Checking filesystem on /dev/md1
UUID: e16cc571-d897-473a-91d3-7673ea91d4cc
Creating a new extent tree
Failed to find [12968716681216, 168, 16384]
btrfs unable to find ref byte nr 12968927035392 parent 0 root 1 owner
1 offset 0
Failed to find [12968716730368, 168, 16384]
btrfs unable to find ref byte nr 12969060089856 parent 0 root 1 owner
0 offset 1
parent transid verify failed on 1103806464 wanted 19 found 13821
Ignoring transid failure
Failed to find [12968716779520, 168, 16384]
btrfs unable to find ref byte nr 12968933851136 parent 0 root 1 owner
0 offset 1
Does it mean something screwed up and unrecoverable?
Hard to say yet.
Is that the only error?
And did you tried btrfsck --init-extent-tree alone?
Although IIRC --init-extent-tree implies --repair, but it seems that
extent tree is not correctly rebuilt at least.
But you must ensure other tree is not corrupted, by using btrfsck without
any option to check the filesystem.
I did run btrfs check --repair without other options.
Oh, I was meant to execute "btrfs check" without any other options,
especially exclude "--repair"...
Finished without
problems as far as i understand the output.
That's a good news, at least it doesn't make the problem worse.
And, it would be quite helpful if you can post all the output(for both
btrfsck --init-extent-tree, and btrfsck), to give us a better view of
what's going wrong.
Thanks,
Qu
Also tried mount with -o
clear_cache. All this doesn't seem to help - tried rsync after that
and the FS went read only with the same error message.
--
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
