All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.ru>
To: Hugo Mills <hugo@carfax.org.uk>
Cc: "Rick Liu" <rickliu@broadcom.com>,
	"Joshua Schüler" <joshua.schueler@gmail.com>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: how to resize (grow) device partition of a multi-device BTRFS filesystem?
Date: Sat, 12 Jan 2013 17:06:45 +0600	[thread overview]
Message-ID: <20130112170645.3214f437@natsu> (raw)
In-Reply-To: <20130112022848.GX19051@carfax.org.uk>

[-- Attachment #1: Type: text/plain, Size: 869 bytes --]

On Sat, 12 Jan 2013 02:28:49 +0000
Hugo Mills <hugo@carfax.org.uk> wrote:

> As long as the start of the partition isn't changed, deleting and
> resizing in fdisk isn't damaging. It's just... slightly disconcerting.
> :)

For that reason I very much prefer the cfdisk implementation from the
gnu-fdisk package. It has an option to really resize the partition. While
resizing the filesystem within it will usually fail, the dialog goes like this:

Select the patition, click "Resize".

"Failed to resize filesystem, change partition size (EXPERT)?" - "Yes"

"Start location? [Fixed start], [Specify different]?" - "Fixed start"

"Partition size? [Max is nnnnMB]" - "nnnnMB".

Done.

-- 
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 --]

  parent reply	other threads:[~2013-01-12 11:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-12  2:18 how to resize (grow) device partition of a multi-device BTRFS filesystem? Rick Liu
2013-01-12  2:28 ` Hugo Mills
2013-01-12  3:11   ` Chris Murphy
2013-01-12 11:06   ` Roman Mamedov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-01-12  0:29 Rick Liu
2013-01-12  1:50 ` Hugo Mills
2013-01-11 23:39 Rick Liu
2013-01-11 23:53 ` Joshua Schüler

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=20130112170645.3214f437@natsu \
    --to=rm@romanrm.ru \
    --cc=hugo@carfax.org.uk \
    --cc=joshua.schueler@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=rickliu@broadcom.com \
    /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.