From: Anand Jain <Anand.Jain@oracle.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Jon Nelson <jnelson@jamponi.net>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs-show vs. btrfs different output
Date: Fri, 22 Mar 2013 11:06:25 +0800 [thread overview]
Message-ID: <514BCAB1.6040608@oracle.com> (raw)
In-Reply-To: <514B346D.1010403@redhat.com>
> What we really need is the right bits in the right places
> to let the administrator know if a device looks like it might
> be corrupt & in need of fixing, vs. ignoring it altogether.
--
> 2. the current git btrfs-show and btrfs fi show both output
> *different* devices for device with UUID
> b5dc52bd-21bf-4173-8049-d54d88c82240, and they're both wrong.
--
here per Jon experience showing stale btrfs on /dev/sdb (note
that good btrfs is on /dev/sdb3) is wrong.
More over when we show something like /dev/sdb and /dev/sdb3
both have two different btrfs, its a bit scary.
I would vote for ignoring it altogether since we have
btrfs-find-root and btrfs-select-super to help find the
backup SB for recovery if needed.
Thanks.
-Anand
next prev parent reply other threads:[~2013-03-22 3:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 15:04 btrfs-show vs. btrfs different output Jon Nelson
2013-03-21 15:11 ` Eric Sandeen
2013-03-21 15:29 ` Jon Nelson
2013-03-21 15:33 ` Helmut Hullen
2013-03-21 16:25 ` Eric Sandeen
2013-03-22 3:06 ` Anand Jain [this message]
2013-03-22 13:59 ` Jon Nelson
2013-03-22 22:34 ` Eric Sandeen
2013-03-21 15:35 ` Helmut Hullen
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=514BCAB1.6040608@oracle.com \
--to=anand.jain@oracle.com \
--cc=jnelson@jamponi.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=sandeen@redhat.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.