From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.gmx.net ([212.227.15.18]:62902 "EHLO mout.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751579AbbKRM3U (ORCPT ); Wed, 18 Nov 2015 07:29:20 -0500 Subject: Re: Transaction aborted (error -17) after crash To: Mordechay Kaganer , Qu Wenruo References: <564BEA55.4040209@gmx.com> <564C0D18.6040802@cn.fujitsu.com> Cc: Btrfs BTRFS From: Qu Wenruo Message-ID: <564C6F09.9090400@gmx.com> Date: Wed, 18 Nov 2015 20:28:57 +0800 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Sender: linux-btrfs-owner@vger.kernel.org List-ID: 在 2015年11月18日 20:02, Mordechay Kaganer 写道: > B.H. > > On Wed, Nov 18, 2015 at 7:31 AM, Qu Wenruo 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? > If it's OK for you, then it's OK BTW, did you run btrfsck *after* --init-extent-tree, *without* --repair? I think it would be much better to do the last btrfsck. And if the last one reports no error, and btrfs still hits the same problem, I think it's time to rebuild the backup.... Thanks, Qu