All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ric Wheeler <ricwheeler@gmail.com>
To: Wendy Cheng <s.wendy.cheng@gmail.com>,
	Linux FS Devel <linux-fsdevel@vger.kernel.org>,
	device-mapper development <dm-devel@redhat.com>,
	Karel Zak <kzak@redhat.com>, Jim Meyering <jim@>
Subject: Re: [dm-devel] generic wrappers for multi-device FS operations
Date: Wed, 09 Mar 2011 10:13:50 -0500	[thread overview]
Message-ID: <4D77992E.1020909@gmail.com> (raw)
In-Reply-To: <20110309142325.GA11312@agk-dp.fab.redhat.com>

On 03/09/2011 09:23 AM, Alasdair G Kergon wrote:
> On Tue, Mar 08, 2011 at 10:05:40AM -0800, Wendy Cheng wrote:
>> So the "resize" is on the filesystem, not the volume ? The "grow" part
>> is probably easy. Unfortunately, the "shrink" may not be easy for some
>> of the filesystems:
> The LVM situation today works both ways around.
>
> You can use 'lvresize' with an option to resize the filesystem too,
> or use 'fsadm' with an option to resize the LV.  We felt that 'fsadm'
> was a more-natural approach: allow the user to resize their filesystem
> and automatically adjust the things underneath as necessary.
>
> Long term, we'd like it to be possible to configure a system for resizing
> entire device stacks both top down (fsadm) and bottom up (triggered by the
> appropriate Unit Attention).
>
> (The current fsadm script was written as a proof-of-concept under the
> constraint of just wrapping existing binaries. Of course there are cleaner
> ways to do it when you allow filesystem-specific code.)
>
> Alasdair

Is anyone actively looking at taken it beyond proof of concept?

Ric


WARNING: multiple messages have this Message-ID (diff)
From: Ric Wheeler <ricwheeler@gmail.com>
To: Wendy Cheng <s.wendy.cheng@gmail.com>,
	Linux FS Devel <linux-fsdevel@vger.kernel.org>,
	device-mapper development <dm-devel@redhat.com>,
	Karel Zak <kzak@redhat.com>, Jim Meyering <jim@
Subject: Re: [dm-devel] generic wrappers for multi-device FS operations
Date: Wed, 09 Mar 2011 10:13:50 -0500	[thread overview]
Message-ID: <4D77992E.1020909@gmail.com> (raw)
In-Reply-To: <20110309142325.GA11312@agk-dp.fab.redhat.com>

On 03/09/2011 09:23 AM, Alasdair G Kergon wrote:
> On Tue, Mar 08, 2011 at 10:05:40AM -0800, Wendy Cheng wrote:
>> So the "resize" is on the filesystem, not the volume ? The "grow" part
>> is probably easy. Unfortunately, the "shrink" may not be easy for some
>> of the filesystems:
> The LVM situation today works both ways around.
>
> You can use 'lvresize' with an option to resize the filesystem too,
> or use 'fsadm' with an option to resize the LV.  We felt that 'fsadm'
> was a more-natural approach: allow the user to resize their filesystem
> and automatically adjust the things underneath as necessary.
>
> Long term, we'd like it to be possible to configure a system for resizing
> entire device stacks both top down (fsadm) and bottom up (triggered by the
> appropriate Unit Attention).
>
> (The current fsadm script was written as a proof-of-concept under the
> constraint of just wrapping existing binaries. Of course there are cleaner
> ways to do it when you allow filesystem-specific code.)
>
> Alasdair

Is anyone actively looking at taken it beyond proof of concept?

Ric


  reply	other threads:[~2011-03-09 15:13 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-08 17:04 generic wrappers for multi-device FS operations Ric Wheeler
2011-03-08 17:04 ` Ric Wheeler
2011-03-08 17:43 ` [dm-devel] " Alasdair G Kergon
2011-03-08 18:05   ` Wendy Cheng
2011-03-08 18:05     ` Wendy Cheng
2011-03-08 18:13     ` Ric Wheeler
2011-03-08 18:34       ` James Bottomley
2011-03-08 18:51         ` Ric Wheeler
2011-03-08 20:16         ` Lars Marowsky-Bree
2011-03-08 18:37     ` Josef Bacik
2011-03-08 18:51       ` Ric Wheeler
2011-03-09 14:23     ` Alasdair G Kergon
2011-03-09 14:23       ` Alasdair G Kergon
2011-03-09 15:13       ` Ric Wheeler [this message]
2011-03-09 15:13         ` Ric Wheeler
2011-03-10 15:28         ` Hannes Reinecke
2011-03-10 15:30           ` Ric Wheeler
2011-03-09 21:36       ` Dave Chinner
2011-03-09 21:36         ` Dave Chinner
2011-03-09 21:49         ` Alasdair G Kergon
2011-03-09 21:49           ` Alasdair G Kergon
2011-03-10  5:04           ` Dave Chinner
2011-03-10  5:04             ` Dave Chinner
2011-03-08 20:54 ` Andreas Dilger
2011-03-08 20:58   ` Ric Wheeler
2011-03-08 22:23     ` Zdenek Kabelac
2011-03-09  2:11   ` Dave Chinner

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=4D77992E.1020909@gmail.com \
    --to=ricwheeler@gmail.com \
    --cc=dm-devel@redhat.com \
    --cc=kzak@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=s.wendy.cheng@gmail.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.