linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Sebastian 'gonX' Jensen" <gonx@overclocked.net>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: How to expand a BTRFS partition... backwards
Date: Sun, 2 May 2010 07:32:34 +0200	[thread overview]
Message-ID: <j2v8a48dc7a1005012232pa765876fscc41e97b940333de@mail.gmail.com> (raw)

Hey guys,

I kinda figured out the syntax for resizing BTRFS arrays, but is it
possible to use free space that is behind the current BTRFS partition?
I kinda figure it's not, but ideally I'd like it so that there is no
unused disk space on the disk.

My partition setup looks something like this:

Partition 1: 100MB (used)
Partition 2: 256MB (not used, this is what I want to use)
Partition 3: 200GB (used, for BTRFS)
Partition 4: 50GB (not used, but this will be expanded to the current
BTRFS partition)

Also as a last note (just in case I've misunderstood something), to
resize properly, you should first delete the partition using a
partition editor like fdisk, then recreate a new partition with the
same start cylinders as the original setup, but with bigger/later end
cylinders than the original setup, right? Then e.g. btrfsctl -r +45G /
What if I have a RAID-0 array (which I do), which uses the RAID-0
routine by BTRFS (and not mdraid or dmraid). Should I then do a
"btrfsctl -R +(size*disks)G /" or btrfsctl -R +(size of all disks)G
/"?

Regards,
Sebastian J.

             reply	other threads:[~2010-05-02  5:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-02  5:32 Sebastian 'gonX' Jensen [this message]
     [not found] ` <4BDD128C.7020606@a-city.de>
2010-05-02  6:23   ` How to expand a BTRFS partition... backwards Sebastian 'gonX' Jensen
2010-05-02  8:10     ` TAXI
     [not found] ` <j2tfc5ef2e01005021409u75d9a45fk2002e2f0f440dde5@mail.gmail.com>
     [not found]   ` <y2q8a48dc7a1005021718j3c6256f9n31ada79603893d1d@mail.gmail.com>
2010-05-03  3:15     ` Sebastian 'gonX' Jensen

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=j2v8a48dc7a1005012232pa765876fscc41e97b940333de@mail.gmail.com \
    --to=gonx@overclocked.net \
    --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).