From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: Marc MERLIN <marc@merlins.org>
Cc: David Sterba <dsterba@suse.cz>,
Btrfs mailing list <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs-image failure (btrfs-tools 4.4)
Date: Mon, 15 Feb 2016 08:17:32 +0800 [thread overview]
Message-ID: <56C1191C.7030309@cn.fujitsu.com> (raw)
In-Reply-To: <20160214172659.GD4115@merlins.org>
Marc MERLIN wrote on 2016/02/14 09:26 -0800:
> On Fri, Feb 12, 2016 at 09:26:28AM -0800, Marc MERLIN wrote:
>> On Fri, Feb 12, 2016 at 08:33:11AM +0800, Qu Wenruo wrote:
>>> There is still a last chance.
>>>
>>> If btrfsck still report original error about "bad file extent" in root:
>>> 45851/45852/...
>>> Btrfs-debug-tree may provide useful info by dumping only that root.
>>>
>>> # btrfs-debug-tree -t 45851
>>>
>>> But the problem is, there is no filename fuzz option.
>>> You need to mask all the filenames in INODE_REF/DIR_ITEM/DIR_INDEX by
>>> script, or just grep the affected inode info following the pattern "key
>>> (<INODE_NUM>".
>>>
>>> At least this should tell us what's the problem and we can check
>>> manually to determine if it's fixable.
>>
>> Mmmh, so the fsck is looking a bit worse now, here is the output:
>> http://marc.merlins.org/tmp/ggm-broken-ds1-fsck.txt
>>
>> I'm not super sure what inode I should use for debug tree. Can you suggest
>> one?
>>
>> I ran the dump
>> gargamel:~# btrfs-image -s -c 9 /dev/mapper/dshelf1old
>> /mnt/dshelf1/ds1old.dump
>> Error adding space cache blocks -5
>> Error flushing pending -5
>> create failed (Success)
>>
>> and a du every so often showed the file go to 9.3GB before btrfs-image
>> deleted it:
>> 9.3G /mnt/dshelf1/ds1old.dump
>
> So I'm at a point where I need to delete this filesystem. I believe it'll be
> monday morning soon on your side of the world :)
> Can you let me know if there is anything else I can/should get before I wipe
> it?
>
> Thanks,
> Marc
>
Sorry for the late reply.
According to the output of your btrfsck --repair output, things just get
worse.
So at this point, it's harder to locate the original problem. (Csum
missing with bad file extents)
IMHO you can wipe the fs now.
Thanks,
Qu
next prev parent reply other threads:[~2016-02-15 0:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 0:27 BTRFS: bdev /dev/mapper/dshelf1 errs: wr 2970, rd 848, flush 0, corrupt 189, gen 0 Marc MERLIN
2016-01-18 3:21 ` Duncan
2016-01-18 23:39 ` Marc MERLIN
2016-01-19 9:39 ` Duncan
2016-01-21 4:52 ` Marc MERLIN
2016-01-23 17:03 ` Marc MERLIN
2016-01-23 23:13 ` Marc MERLIN
2016-01-25 1:37 ` Qu Wenruo
2016-01-25 15:55 ` 4.4.0: btrfs-send BUG_ON(sctx->cur_ino != sctx->cmp_key->objectid); Marc MERLIN
2016-01-25 19:46 ` Filipe Manana
2016-01-25 19:56 ` Marc MERLIN
2016-01-25 20:24 ` Filipe Manana
2016-01-25 21:21 ` Marc MERLIN
2016-01-25 20:55 ` BTRFS: bdev /dev/mapper/dshelf1 errs: wr 2970, rd 848, flush 0, corrupt 189, gen 0 Marc MERLIN
2016-01-26 1:03 ` Qu Wenruo
2016-02-11 6:31 ` btrfs-image failure (btrfs-tools 4.4) Marc MERLIN
2016-02-11 7:16 ` Qu Wenruo
2016-02-11 15:09 ` Marc MERLIN
2016-02-11 15:13 ` Marc MERLIN
2016-02-12 0:33 ` Qu Wenruo
2016-02-12 17:26 ` Marc MERLIN
2016-02-14 17:26 ` Marc MERLIN
2016-02-15 0:17 ` Qu Wenruo [this message]
2016-02-15 16:40 ` Marc MERLIN
2016-01-18 12:45 ` BTRFS: bdev /dev/mapper/dshelf1 errs: wr 2970, rd 848, flush 0, corrupt 189, gen 0 Hugo Mills
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56C1191C.7030309@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=marc@merlins.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).