From: Marcel Lohmann <marcel.lohmann@googlemail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs on LVM: Out of space
Date: Wed, 8 Sep 2010 22:35:03 +0200 [thread overview]
Message-ID: <AANLkTini5k0cOwCW5WrZuw3M0ynDy8v9MbSyzPGMRmZy@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimLFf-GezTk07NCQjNKkB5RyVge81kzhs27=jAb@mail.gmail.com>
2010/9/8 Zhu Yanhai <zhu.yanhai@gmail.com>:
> Hi,
> Have you ever tried with 'mkfs.btrfs -m single /dev/xxxx'?
> As you had a RAID1 based on LVM, you don't have to keep
> the default duplicated metadata profile in Btrfs.
>
> -zyh
>
> 2010/9/8 Marcel Lohmann <marcel.lohmann@googlemail.com>:
>> In that complete logical volume I created a btrfs partition. And
>> btrfs-show displays 130GB space. Fine.
>> to give me the actual numbers. And that tells me:
>> Data: total=23.97GB, used=23.97GB
>> Metadata: total=53.01GB, used=33.98GB
>> System: total=12.00MB, used=16.00KB
No, I did not try this. I just created it with the defaults
"mkfs.btrfs /dev/mapper/somelogicalvolume". Isn't "-m single" the
default?
So is it right that btrfs "knows" that it is running on a RAID and
changes it's behavior? Why? Normally a FS does not care about the
underlaying (hidden) disk array.
But if it is neccessary to "drop" that duplicate metadata, how can I
arrange this afterwards. And if it is done, then I would have reduced
the Metadata size, but will there really be more space for Data? Where
is the remaining space from 77 GB to 130 GB?
Maybe I was pointing it the wrong way, sorry. I created a mdadm
software RAID1 and on that is a LVM. I did not use btrfs to span over
two disks. The md RAID with LVS was there before and I couldn't change
this.
This is why I have no btrfs-RAID but a md-RAID.
Marcel
next prev parent reply other threads:[~2010-09-08 20:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 11:18 btrfs on LVM: Out of space Marcel Lohmann
2010-09-08 14:53 ` Zhu Yanhai
2010-09-08 20:35 ` Marcel Lohmann [this message]
2010-09-09 2:15 ` Zhu Yanhai
2010-09-09 9:23 ` Marcel Lohmann
2010-09-09 9:37 ` Tamás Gulácsi
2010-09-09 9:52 ` Zhu Yanhai
2010-09-09 10:54 ` Marcel Lohmann
2010-09-10 19:46 ` Marcel Lohmann
2010-09-17 15:29 ` Johannes Hirte
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=AANLkTini5k0cOwCW5WrZuw3M0ynDy8v9MbSyzPGMRmZy@mail.gmail.com \
--to=marcel.lohmann@googlemail.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).