public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@lichtvoll.de>
To: "linux-btrfs" <linux-btrfs@vger.kernel.org>,
	Miguel F Mascarenhas Sousa Filipe <miguel.filipe@gmail.com>
Subject: Re: Fwd: btrfs-tools backport for Debian Lenny
Date: Wed, 17 Feb 2010 19:12:19 +0100	[thread overview]
Message-ID: <201002171912.25830.Martin@lichtvoll.de> (raw)
In-Reply-To: <f058a9c31002170922y2566427dpd5006c1c0298a444@mail.gmail.com>

[-- Attachment #1: Type: Text/Plain, Size: 1700 bytes --]

Am Mittwoch 17 Februar 2010 schrieben Sie:
> On Wed, Feb 17, 2010 at 3:32 PM, Martin Steigerwald <ms@teamix.de> 
wrote:

Leaving Cc to backports-users mailinglist and Debian package maintainer 
dropped as its a technical BTRFS discussion.

> > Hi!
[...]
> > It basically works, but I am wondering it the RAID options work
> > correctly. I used:
> >
> > mkfs.btrfs -d raid1 -m
> > raid1 /dev/mango1/homelokal1 /dev/mango2/homelokal2
> >
> > on two 200 GiB logical volumes and get
> >
> > mango:~# df -hT /mnt/zeit
> > Dateisystem   Typ    Größe Benut  Verf Ben% Eingehängt auf
> > /dev/mapper/mango1-homelokal1
> >             btrfs    400G  101M  400G   1% /mnt/zeit
> >
> > Shouldn't that be 200GiB for a BTRFS Raid 1 setup?
> 
> this has been discussed several times on the list.

Sorry, I admit I follow BTRFS irregularily and main point in my mail was 
to announce the backport.

> Since btrfs file level redundancy policy, the proper way for it to
> behave is to show full physical capacity of the devices.
> Usage will be correctly accounted, so if you write a 100MB file in
> that raid1 FS tree
> the used space will indicate 200MB of additional used space.

Hmmm, that still doesn't match, cause I wrote a 100MiB file to the 
partition:

mango:~# dd if=/dev/zero of=/mnt/zeit/ddimg bs=1M count=100
100+0 Datensätze ein
100+0 Datensätze aus
104857600 Bytes (105 MB) kopiert, 0,313594 s, 334 MB/s

Thus I should have get 200MiB used in df -h. Hmmm, maybe accurate size 
reporting needs a newer BTRFS than in 2.6.32.3?

Ciao,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2010-02-17 18:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-17 15:32 btrfs-tools backport for Debian Lenny Martin Steigerwald
2010-02-17 17:21 ` Miguel F Mascarenhas Sousa Filipe
2010-02-17 17:22   ` Fwd: " Miguel F Mascarenhas Sousa Filipe
2010-02-17 18:12     ` Martin Steigerwald [this message]

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=201002171912.25830.Martin@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=miguel.filipe@gmail.com \
    /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