B.H. On Wed, Nov 18, 2015 at 7:31 AM, Qu Wenruo <quwenruo@xxxxxxxxxxxxxx> wrote: > > 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. btrfs check --init-extent-tree --repair gives tons of messages like this: ref mismatch on [1628438528 16384] extent item 0, found 1 adding new tree backref on start 1628438528 len 16384 parent 0 root 258 Backref 1628438528 parent 258 root 258 not found in extent tree backpointer mismatch on [1628438528 16384] ref mismatch on [1628454912 16384] extent item 0, found 1 adding new tree backref on start 1628454912 len 16384 parent 0 root 7 Backref 1628454912 parent 7 root 7 not found in extent tree backpointer mismatch on [1628454912 16384] ref mismatch on [1628471296 16384] extent item 0, found 1 adding new tree backref on start 1628471296 len 16384 parent 0 root 7 Backref 1628471296 parent 7 root 7 not found in extent tree backpointer mismatch on [1628471296 16384] ref mismatch on [1628487680 16384] extent item 0, found 1 adding new tree backref on start 1628487680 len 16384 parent 0 root 7 Backref 1628487680 parent 7 root 7 not found in extent tree backpointer mismatch on [1628487680 16384] Anyway, that's only a backup so i think it's better to rebuild it from scratch, right? -- "ויעקב הלך לדרכו..." משיח NOW! Moshiach is coming very soon, prepare yourself! יחי אדוננו מורינו ורבינו מלך המשיח לעולם ועד! -- 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
