From: Roman Mamedov <rm@romanrm.ru>
To: "Swâmi Petaramesh" <swami@petaramesh.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Change "small" filesystem to normal
Date: Sun, 22 Jul 2012 21:37:14 +0600 [thread overview]
Message-ID: <20120722213714.2b5be0e1@natsu> (raw)
In-Reply-To: <500C16F0.6000205@petaramesh.org>
[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]
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
--
With respect,
Roman
~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Stallman had a printer,
with code he could not see.
So he began to tinker,
and set the software free."
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-07-22 15:37 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 [this message]
2012-07-23 4:55 ` Swâmi Petaramesh
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=20120722213714.2b5be0e1@natsu \
--to=rm@romanrm.ru \
--cc=linux-btrfs@vger.kernel.org \
--cc=swami@petaramesh.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 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.