From: Ilya Dryomov <idryomov@gmail.com>
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 18:14:00 +0300 [thread overview]
Message-ID: <20120722151400.GA1934@zambezi.lan> (raw)
In-Reply-To: <500C16F0.6000205@petaramesh.org>
On Sun, Jul 22, 2012 at 05:06:24PM +0200, Swâmi Petaramesh 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.
>
> Is there a way tp do this without reformatting the FS ?
No, currently there is no way to do this. You'll have to create a new
filesystem with mkfs.btrfs.
Thanks,
Ilya
next prev parent reply other threads:[~2012-07-22 15:14 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 [this message]
2012-07-22 15:37 ` Roman Mamedov
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=20120722151400.GA1934@zambezi.lan \
--to=idryomov@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox