linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: gmack@innerfire.net
To: linux-btrfs@vger.kernel.org
Subject: raid1 not reporting the right size
Date: Thu, 27 May 2010 15:43:05 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.1.10.1005271527320.19767@mtl.rackplans.net> (raw)

I'm trying to create a raid1 (mirrored) raid using two 1 Tb disks.
The result is something twice as large as it should be fore mirrored raid.

Any ideas? Linux version 2.6.34

# mkfs.btrfs -d raid1 -m raid1 /dev/sdb1 /dev/sdc1 -L fhome

WARNING! - Btrfs Btrfs v0.19 IS EXPERIMENTAL
WARNING! - see http://btrfs.wiki.kernel.org before using

adding device /dev/sdc1 id 2
fs created label fhome on /dev/sdb1
        nodesize 4096 leafsize 4096 sectorsize 4096 size 1.82TB
Btrfs Btrfs v0.19

# mount /dev/sdb1 /mnt/
# df -h /mnt/
Filesystem            Size  Used Avail Use% Mounted on
/dev/sdb1             1.9T   56K  1.9T   1% /mnt

# btrfs-show
failed to read /dev/sr0
Label: none  uuid: a2aa44b8-3168-480a-a155-d510e05853e7
        Total devices 1 FS bytes used 617.45MB
        devid    1 size 29.33GB used 6.79GB path /dev/sda2

Label: fhome  uuid: 128ddab5-224d-4f45-abc0-6a07d0f63d47
        Total devices 2 FS bytes used 28.00KB
        devid    2 size 931.51GB used 2.01GB path /dev/sdc1
        devid    1 size 931.51GB used 2.03GB path /dev/sdb1

--
Gerhard Mack

gmack@innerfire.net

<>< As a computer I find your faith in technology amusing.

             reply	other threads:[~2010-05-27 19:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-27 19:43 gmack [this message]
2010-05-27 19:51 ` raid1 not reporting the right size Chris Ball
2010-05-28 18:45   ` linux 2.6.34 raid1 btrfs weird mounting issue gmack
2010-05-28 18:52     ` Sebastian 'gonX' Jensen
2010-05-28 19:06     ` Goffredo Baroncelli
2010-05-27 20:04 ` raid1 not reporting the right size 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=alpine.DEB.1.10.1005271527320.19767@mtl.rackplans.net \
    --to=gmack@innerfire.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 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).