From: "Cyril B. " <cbay@excellency.fr>
To: linux-btrfs@vger.kernel.org
Subject: mkfs devices ordering relevant with devices of different sizes?
Date: Wed, 25 Jul 2012 15:26:20 +0200 [thread overview]
Message-ID: <juos5r$2tp$1@dough.gmane.org> (raw)
Hello,
When creating a filesystem with devices of different sizes, the resulting
filesystem total size depends on the device order specified to mkfs. When
the smaller device is specified first, the second (larger) device is seen as
the same size as the first. This doesn't occur when the order is reversed.
It's confusing. Is this expected? I'm using the latest btrfs-progs and Linux
3.5.
# ./mkfs.btrfs /dev/sda4 /dev/sdc
WARNING! - Btrfs Btrfs v0.19 IS EXPERIMENTAL
WARNING! - see http://btrfs.wiki.kernel.org before using
adding device /dev/sdc id 2
fs created label (null) on /dev/sda4
nodesize 4096 leafsize 4096 sectorsize 4096 size 3.97TB
Btrfs Btrfs v0.19
backup6:~/btrfs-progs# ./btrfs fi show /dev/sdc
Label: none uuid: 806b237e-53ed-409e-a7c1-02f101798384
Total devices 2 FS bytes used 28.00KB
devid 2 size 1.98TB used 2.01GB path /dev/sdc
devid 1 size 1.98TB used 2.03GB path /dev/sda4
Btrfs Btrfs v0.19
# ./mkfs.btrfs /dev/sdc /dev/sda4
WARNING! - Btrfs Btrfs v0.19 IS EXPERIMENTAL
WARNING! - see http://btrfs.wiki.kernel.org before using
adding device /dev/sda4 id 2
fs created label (null) on /dev/sdc
nodesize 4096 leafsize 4096 sectorsize 4096 size 4.71TB
Btrfs Btrfs v0.19
backup6:~/btrfs-progs# ./btrfs fi show /dev/sdc
Label: none uuid: 8f99c072-521b-4827-a2be-41de6ab11b4f
Total devices 2 FS bytes used 28.00KB
devid 1 size 2.73TB used 2.03GB path /dev/sdc
devid 2 size 1.98TB used 2.01GB path /dev/sda4
Btrfs Btrfs v0.19
Thanks.
--
Cyril B.
next reply other threads:[~2012-07-25 13:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 13:26 Cyril B. [this message]
2012-07-26 21:09 ` mkfs devices ordering relevant with devices of different sizes? David Sterba
2012-07-27 12:05 ` Josef Bacik
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='juos5r$2tp$1@dough.gmane.org' \
--to=cbay@excellency.fr \
--cc=cbay@alwaysdata.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;
as well as URLs for NNTP newsgroup(s).