public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Roland Dreier <rdreier@cisco.com>
To: linux-btrfs@vger.kernel.org
Subject: UI issues around RAID1
Date: Mon, 16 Nov 2009 10:45:28 -0800	[thread overview]
Message-ID: <adapr7ib96f.fsf@roland-alpha.cisco.com> (raw)

I've just started playing around with btrfs RAID1, and I've noticed a
couple of what seem to be UI issues.  Suppose I do something like
"mkfs.btrfs -d raid1 -m raid1 dev1 dev2".  I see the following minor
usability problems:

 - Unless I'm missing something, there doesn't seem to be any way later
   on to see that I set the data policy to raid1, except using
   btrfs-dump-tree and checking the flags bits for the appropriate
   group.  Which can make things confusing if I have a bunch of btrfs
   filesystems around.

 - The free space reporting doesn't seem to take into account the fact
   that everything is going to be mirrored; so "df" et al report the
   size of the filesystem and free space on the new filesystem as
   size(dev1) + size(dev2) -- if dev1 and dev2 are the same size then I
   would assume it should really be just size(dev1) for a fully-RAID1
   filesystem.  (Not sure in general what we should say for a
   metadata-only mirrored filesystem, since we don't really know in
   advance how much space we have exactly)

I'm happy to help fix these issues up; just want to make sure I'm not
missing something or doing it wrong.

Thanks,
  Roland

             reply	other threads:[~2009-11-16 18:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-16 18:45 Roland Dreier [this message]
2009-11-16 20:20 ` UI issues around RAID1 Josef Bacik
2009-11-16 21:48   ` jim owens
     [not found]     ` <2a31deca0911170244m74478cefy2a3f5f7bc1daf476@mail.gmail.com>
2009-11-17 15:25       ` jim owens
2009-11-17 20:23         ` Andrey Kuzmin
2009-11-18 17:59     ` Roland Dreier
2009-11-19 14:56       ` Chris Mason
2009-11-18 17:54   ` Roland Dreier

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=adapr7ib96f.fsf@roland-alpha.cisco.com \
    --to=rdreier@cisco.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox