From: "Swâmi Petaramesh" <swami@petaramesh.org>
To: Roman Mamedov <rm@romanrm.ru>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Change "small" filesystem to normal
Date: Mon, 23 Jul 2012 06:55:26 +0200 [thread overview]
Message-ID: <500CD93E.9040207@petaramesh.org> (raw)
In-Reply-To: <20120722213714.2b5be0e1@natsu>
You're painfully right Roman,
A freshly formatted 1 GB BTRFS filesystem on which 81 MB of data has
been put shows only ~260 MB of free space and reserves something like 2
x 380 MB of metadata.
This is absolutely ridiculous of BTRFS... :-/
Kind regards.
Le 22/07/2012 17:37, Roman Mamedov a écrit :
> On Sun, 22 Jul 2012 17:06:24 +0200
> Swâmi Petaramesh <swami@petaramesh.org> wrote:
>
>> Hi,
>>
>> I've created a "small" BTRFS filesystem, where metadata+data are mixed
>> (and metadata are not DUP'ed).
>>
>> Then I've enlarged the FS to 1 GB ; now I'd like to make it "normal"
>> with separate data and metadata, and "DUP'ed" metadata.
> Considering the metadata overallocation bug [1] is still not fixed even in the
> latest kernels and no one seems to care all that much, I would not recommend
> doing that.
>
> Personally I now use a "mixed" filesystem on a 1TB disk without any problems,
> and do not think there's anything wrong with "mixed". In fact there's been
> some talk of moving to the mixed mode allocation to be used by default, and
> maybe even removing support for the "split" mode: see [2].
>
> [1] http://comments.gmane.org/gmane.comp.file-systems.btrfs/17848
>
> [2] http://kerneltrap.org/mailarchive/linux-btrfs/2010/10/29/6885925
>
>
next prev parent reply other threads:[~2012-07-23 4:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-22 15:06 Change "small" filesystem to normal Swâmi Petaramesh
2012-07-22 15:14 ` Ilya Dryomov
2012-07-22 15:37 ` Roman Mamedov
2012-07-23 4:55 ` Swâmi Petaramesh [this message]
2012-07-23 5:50 ` cwillu
2012-07-23 5:51 ` 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=500CD93E.9040207@petaramesh.org \
--to=swami@petaramesh.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=rm@romanrm.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.