From: Anand Jain <Anand.Jain@oracle.com>
To: Gene Czarcinski <gene@czarc.net>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs fi show
Date: Mon, 18 Nov 2013 10:17:19 +0800 [thread overview]
Message-ID: <528978AF.3020806@oracle.com> (raw)
In-Reply-To: <528787FB.4040100@czarc.net>
There is a fix for this (which David has integrated into the branch
recently). This also needs the kernel side patch which is listed below.
[PATCH v4 1/3] btrfs-progs: mechanism to fetch fsinfo from btrfs-control
[PATCH v4 2/3] btrfs-progs: fs show should handle if subvol(s) mounted
[PATCH v2] btrfs: add framework to read fs info from btrfs-control
Thanks, Anand
On 11/16/2013 10:58 PM, Gene Czarcinski wrote:
> I am on Fedora 20-Beta and we just updated to btrfs-progs
> 0.20.rc1-20131114git9f0c53f
>
> Previously, when you did a btrfs fi show, you got a list with one output
> for each btrfs storage volume whether it was a single device or
> multi-device volume.
>
> Now, I get multiple outputs for each storage volume. For example, I
> have a system with two SSDs as one btrfs storage volume and two USB
> round-and-brown disks as a second btrfs storage volume. Each has three
> subvols defined and mounted.
>
> Previously, I got two outputs; one for each volume.
>
> Now I get three outputs for the SSD storage volume and SIX outputs for
> the out volume.
>
> Is this a bug or a feature? If it is a feature, what is it telling me?
>
> Gene
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-11-18 2:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-16 14:58 btrfs fi show Gene Czarcinski
2013-11-16 16:04 ` Chris Murphy
2013-11-16 20:33 ` Duncan
2013-11-16 21:50 ` Chris Murphy
2013-11-16 22:36 ` Duncan
2013-11-18 2:17 ` Anand Jain [this message]
2013-11-18 19:32 ` Chris Mason
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=528978AF.3020806@oracle.com \
--to=anand.jain@oracle.com \
--cc=gene@czarc.net \
--cc=linux-btrfs@vger.kernel.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.