From: Sean Greenslade <sean@seangreenslade.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Qu Wenruo <quwenruo@cn.fujitsu.com>,
David Sterba <dsterba@suse.cz>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Post ext3 conversion problems
Date: Fri, 16 Sep 2016 20:03:03 -0400 [thread overview]
Message-ID: <20160917000302.GA1156@coach.home> (raw)
In-Reply-To: <CAJCQCtSW0zrWdYgWsWmokBDGBY8Lkd0E-cKKmBf7CfoZdR5aFA@mail.gmail.com>
On Fri, Sep 16, 2016 at 05:45:59PM -0600, Chris Murphy wrote:
> On Fri, Sep 16, 2016 at 5:25 PM, Sean Greenslade
> <sean@seangreenslade.com> wrote:
>
> > In the mean time, is there any way to make the kernel more verbose about
> > btrfs errors? It would be nice to see, for example, what was in the
> > transaction that failed, or at least what files / metadata it was
> > touching.
>
> No idea. Maybe one of the compile time options:
>
>
> CONFIG_BTRFS_FS_CHECK_INTEGRITY=y
> This also requires mount options, either check_int or check_int_data
> CONFIG_BTRFS_FS_RUN_SANITY_TESTS
> CONFIG_BTRFS_DEBUG=y
> https://patchwork.kernel.org/patch/846462/
> CONFIG_BTRFS_ASSERT=y
>
> Actually, even before that maybe if you did a 'btrfs-debug-tree /dev/sdX'
>
> That might explode in the vicinity of the problem. Thing is, btrfs
> check doesn't see anything wrong with the metadata, so chances are
> debug-tree won't either.
Hmm, I'll probably have a go at compiling the latest mainline kernel
with CONFIG_BTRFS_DEBUG enabled. It certainly can't hurt to try.
And as you suspected, btrfs-debug-tree didn't explode / error out on me.
I didn't thoroughly inspect the output (as I have very little
understanding of the btrfs internals), but it all seemed OK.
--Sean
next prev parent reply other threads:[~2016-09-17 0:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 19:25 Post ext3 conversion problems Sean Greenslade
2016-09-16 20:23 ` Chris Murphy
2016-09-16 23:25 ` Sean Greenslade
2016-09-16 23:45 ` Chris Murphy
2016-09-17 0:03 ` Sean Greenslade [this message]
2016-09-19 2:20 ` Qu Wenruo
2016-09-19 4:12 ` Sean Greenslade
2016-09-19 6:30 ` Qu Wenruo
2016-09-19 15:13 ` Sean Greenslade
2016-09-20 2:49 ` Qu Wenruo
2016-09-20 3:39 ` Sean Greenslade
2016-09-20 5:02 ` Qu Wenruo
2016-09-20 20:51 ` Sean Greenslade
2016-09-26 2:16 ` Sean Greenslade
2016-09-26 2:37 ` Qu Wenruo
2016-09-17 2:27 ` Liu Bo
2016-09-17 4:16 ` Sean Greenslade
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=20160917000302.GA1156@coach.home \
--to=sean@seangreenslade.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=quwenruo@cn.fujitsu.com \
/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.