public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: planetf1 <bugs@cherrybyte.me.uk>
To: linux-btrfs@vger.kernel.org
Subject: Resizing a btrfs managed partition
Date: Wed, 24 Feb 2010 14:32:50 +0000	[thread overview]
Message-ID: <hm3dai$pnl$1@dough.gmane.org> (raw)

Hi,
  Let me know if this is the wrong place to ask...

  I'm using Fedora 12 x86_64, mostly with the newer 21.6.32 kernel, and 
have a single btrfs filesystem within a 120Gb partition.

  I'd like to extend the space btrfs can use. One option is presumably 
add a new device to btrfs, but I was hoping to simple resize the 
existing partition to say 160Gb.

  With ext4 I might do this with gparted , although mostly I'd use LVM, 
with seperate LVs for /opt /home / etc and that's been the way I've done 
it for many years.

  With btrfs I'm unsure as to the safe steps and decided to skip on use 
of LVM giving the enhanced capabilities of btrfs itself.

  Is it ok to resize the partition with gparted?
  How do I make btrfs use the new partition size?
  Or are there other btrfs specific tools that can manage partitions
  Would I be better off still using lvm in conjunction with btrfs?
  Are there good pointers to useful user material on btrfs on these issues?
  Is creating new subvolumes to manage /home (say I want to limit that 
space, and create snapshots independently) appropriate, and if so what's 
the easiest way to do that -- I had trouble with getting the subvolume 
ops to work

Mostly rather than NEED btrfs per se, I'm using a clean laptop 
environment as a way to experiment with the new filesystem & understand 
how to manage it.

Thanks
Nigel.
bugs@cherrybyte.me.uk



             reply	other threads:[~2010-02-24 14:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-24 14:32 planetf1 [this message]
2010-02-24 17:58 ` Resizing a btrfs managed partition Goffredo Baroncelli
2010-02-25 16:11   ` planetf1

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='hm3dai$pnl$1@dough.gmane.org' \
    --to=bugs@cherrybyte.me.uk \
    --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