From: Chris Mason <chris.mason@oracle.com>
To: Donggeun Kim <dg77.kim@samsung.com>
Cc: linux-btrfs@vger.kernel.org, kyungmin.park@samsung.com
Subject: Re: [PATCH] btrfs: Add a new mount option to grow the FS to the limit of the device
Date: Wed, 4 Aug 2010 09:30:51 -0400 [thread overview]
Message-ID: <20100804133051.GF16630@think> (raw)
In-Reply-To: <4C595053.5030305@samsung.com>
On Wed, Aug 04, 2010 at 08:34:43PM +0900, Donggeun Kim wrote:
> Chris Mason wrote:
> > On Mon, Aug 02, 2010 at 05:42:00PM +0900, Donggeun Kim wrote:
> >> In some cases, resizing a file system to the maximum device size is required.
> >> When flashing a file system image to a block device,
> >> the file system does not fit into the block device's size.
> >> Currently, executing 'btrfsctl' application is the only way
> >> to grow the file system to the limit of the device.
> >> If the mount option which alters the device size of a file system
> >> to the limit of the device is supported,
> >> it can be useful regardless of the existence of 'btrfsctl' program.
> >> This patch allows the file system to grow to the maximum size of the device
> >> on mount time.
> >> The new mount option name is 'maxsize'.
> >
> > I think this is a very useful feature, but could you please change the
> > patch to allow controlling which device is resized?
> >
> > The ioctl allows you to pass in a device number (where the number comes
> > from btrfs-show)
> >
> > Thanks!
> >
> > -chris
> >
> I'm sorry not to fully understand your comment.
> Do you mean that device file name for being resized is specified after 'maxsize' mount option?
> e.g) #mount -o maxsize=/dev/sda1 ...
In the resize ioctl you can pass a device number, something like 2:max,
which allows you to say make device #2 the full size of the device.
btrfs-show can be used to find the correct device number for a given
disk. We don't use the device name because the scan might have found a
different device name to tie into the FS.
Thanks,
Chris
next prev parent reply other threads:[~2010-08-04 13:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 8:42 [PATCH] btrfs: Add a new mount option to grow the FS to the limit of the device Donggeun Kim
2010-08-03 11:49 ` Chris Mason
2010-08-04 11:34 ` Donggeun Kim
2010-08-04 13:30 ` Chris Mason [this message]
2010-08-04 13:45 ` Kyungmin Park
2010-08-04 13:47 ` Chris Mason
2010-08-04 13:56 ` Kyungmin Park
2010-08-04 14:52 ` Chris Mason
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=20100804133051.GF16630@think \
--to=chris.mason@oracle.com \
--cc=dg77.kim@samsung.com \
--cc=kyungmin.park@samsung.com \
--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).