Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Alexander Koch <lynix47@googlemail.com>
To: Hugo Mills <hugo@carfax.org.uk>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs-raid10 <-> btrfs-raid1 confusion
Date: Sun, 06 May 2012 21:49:36 +0200	[thread overview]
Message-ID: <4FA6D5D0.5050501@gmail.com> (raw)
In-Reply-To: <20120506152343.GL9860@carfax.org.uk>

Thanks for clarifying things, Hugo :)

>    It won't -- "btrfs fi df" reports what's been allocated out of the
> raw pool. To check that the disks have been added, you need "btrfs fi
> show" (no parameters).

Okay, that gives me

    Label: 'archive'  uuid: 3818eedb-5379-4c40-9d3d-bd91f60d9094
        Total devices 4 FS bytes used 1.68TB
        devid    4 size 931.51GB used 664.03GB path /dev/dm-10
        devid    3 size 931.51GB used 664.03GB path /dev/dm-9
        devid    2 size 1.82TB used 1.56TB path /dev/dm-8
        devid    1 size 1.82TB used 1.56TB path /dev/dm-7

so I conclude all disks are successfully assigned to the raw pool for my
'archive' volume.


> You're not comparing the right numbers here. "btrfs fi show" shows
> the raw available unallocated space that the filesystem has to play
> with. "btrfs fi df" shows only what it's allocated so far, and how
> much of the atllocation it has used -- in this case, because you've
> added new disks, there's quite a bit of free space unallocated still,
> so the numbers below won't add up to anything like 3TB.

So how is the available space in the raw pool finally allocated to the
usable area? Must I manually enlarge the filesystem by issuing a
'btrfs fi resize max /mountpoint' (like assigning space of a VG to a
logical volume in LVM) or is the space allocated automatically when the
filesystem gets filled with data?


Regards,

Alex

  reply	other threads:[~2012-05-06 19:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-06 14:48 btrfs-raid10 <-> btrfs-raid1 confusion Alexander Koch
2012-05-06 15:23 ` Hugo Mills
2012-05-06 19:49   ` Alexander Koch [this message]
2012-05-06 20:17     ` Hugo Mills
2012-05-06 20:02   ` cwillu

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=4FA6D5D0.5050501@gmail.com \
    --to=lynix47@googlemail.com \
    --cc=hugo@carfax.org.uk \
    --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