From: Chris Mason <clm@fb.com>
To: Marc MERLIN <marc@merlins.org>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: Upgrade to 3.14.0 messed up raid0 array (btrfs cleaner crashes in fs/btrfs/extent-tree.c:5748 and fs/btrfs/free-space-cache.c:1183 )
Date: Wed, 9 Apr 2014 14:54:32 -0400 [thread overview]
Message-ID: <53459768.8020408@fb.com> (raw)
In-Reply-To: <20140409165134.GO10789@merlins.org>
On 04/09/2014 12:51 PM, Marc MERLIN wrote:
> On Wed, Apr 09, 2014 at 11:46:13AM -0400, Chris Mason wrote:
>> Downloading the image now. I'd just run a readonly btrfsck /dev/xxx
>
> https://urldefense.proofpoint.com/v1/url?u=http://marc.merlins.org/tmp/btrfs-raid0-image-fsck.txt&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=6%2FL0lzzDhu0Y1hL9xm%2BQyA%3D%3D%0A&m=FvUwVb5mtQKfcHDJf0YzDhzyfAaFwrR9BXQbyCmT0No%3D%0A&s=633624e090ad2c187c1c5d62169bc0a8470ff2560049f83f195642638bff4b91 (6MB)
>
> I admit to not knowing how to read that output, I've only ever seen
> thousands of lines of output from it on any filesystem., but hopefully you
> know how to grep out expected noise.
>
> But since we're talking about this, is btrfsck ever supposed to return clean
> on a clean filesystem?
Looks like I'm getting different results from btrfsck on the image.
Still a ton of corruptions but complaints about different blocks.
Can you please use btrfs-map-logical to dump both copies of block
245432320 and send me the results?
-chris
next prev parent reply other threads:[~2014-04-09 18:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 15:36 Upgrade to 3.14.0 messed up raid0 array (btrfs cleaner crashes in fs/btrfs/extent-tree.c:5748 and fs/btrfs/free-space-cache.c:1183 ) Marc MERLIN
2014-04-08 22:09 ` Marc MERLIN
2014-04-08 23:49 ` Chris Mason
2014-04-09 4:31 ` Marc MERLIN
2014-04-09 5:31 ` Marc MERLIN
2014-04-09 15:42 ` Marc MERLIN
2014-04-09 15:46 ` Chris Mason
2014-04-09 16:51 ` Marc MERLIN
2014-04-09 18:54 ` Chris Mason [this message]
2014-04-09 19:24 ` Duncan
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=53459768.8020408@fb.com \
--to=clm@fb.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.