linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ric Wheeler <ricwheeler@gmail.com>
To: James Bottomley <James.Bottomley@suse.de>
Cc: 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@meyering.net>,
	Chris Mason <chris.mason@oracle.com>,
	Josef Bacik <josef@redhat.com>
Subject: Re: [dm-devel] generic wrappers for multi-device FS operations
Date: Tue, 08 Mar 2011 13:51:57 -0500	[thread overview]
Message-ID: <4D767ACD.2020506@gmail.com> (raw)
In-Reply-To: <1299609274.2476.180.camel@mulgrave.site>

On 03/08/2011 01:34 PM, James Bottomley wrote:
> On Tue, 2011-03-08 at 13:13 -0500, Ric Wheeler wrote:
>> On 03/08/2011 01:05 PM, Wendy Cheng wrote:
>>>> On Tue, Mar 08, 2011 at 12:04:25PM -0500, Ric Wheeler wrote:
>>>>> To make this trivial to do for users, I think that it would be really
>>>>> nice to have a two-level wrappers for things like resize, add a volume,
>>>>> shrink, etc. Similar to the way we have mount or fsck invoke file system
>>>>> specific bits.
>>>>> Good idea? Bad idea?
>>> 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:
>>>
>>> -- Wendy
>> I think any "standard" operation would be allowed to fail with "notsupported"
>> effectively. Shrink is definitely a challenge&  even when it works, it often has
>> performance implications.
>>
>> I think that adding support to fsadm might be the easy path forward, but we
>> would need to be able to do at least a handful of more advanced things (add a
>> whole device for example).
> There's still the problem of moving the underlying device from being a
> plain block device to being a dm one ... what happened to the idea of
> presenting all devices as dm ones to solve this?
>
> James

I think that would certainly be a nice start, but we could do something short 
term that did not require that.

Ric


  reply	other threads:[~2011-03-08 18:52 UTC|newest]

Thread overview: 19+ 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:43 ` [dm-devel] " Alasdair G Kergon
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 [this message]
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 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:49         ` Alasdair G Kergon
2011-03-10  5:04           ` Dave Chinner
2011-03-08 20:54 ` Andreas Dilger
2011-03-08 20:58   ` Ric Wheeler
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=4D767ACD.2020506@gmail.com \
    --to=ricwheeler@gmail.com \
    --cc=James.Bottomley@suse.de \
    --cc=chris.mason@oracle.com \
    --cc=dm-devel@redhat.com \
    --cc=jim@meyering.net \
    --cc=josef@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 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).