From: Mike Anderson <andmike@linux.vnet.ibm.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: Andrew Patterson <andrew.patterson@hp.com>
Subject: Re: Status of resizing/growing dm-multipath devices on the fly
Date: Wed, 6 Aug 2008 12:36:02 -0700 [thread overview]
Message-ID: <20080806193602.GA9941@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080806143751.GO3771@edu.joroinen.fi>
Pasi K?rkk?inen <pasik@iki.fi> wrote:
> On Wed, Aug 06, 2008 at 03:48:12PM +0200, Domenico Viggiani wrote:
> > * Pasi Kärkkäinen wrote:
> > >
> > > Is it possible to resize (grow) dm-multipath devices on the
> > > fly nowadays?
> > >
> > > I googled and found some discussions about the subject, but
> > > the conclusion seemed to be it's not possible.. that was a
> > > while ago, so I was wondering if this has been fixed/implemented..
> > >
> > > Using LVM and adding another new LUN/PV is not an option
> > > always.. it's a lot easier to manage the whole thing if it's
> > > possible to resize/grow existing LUNs on the fly.
> >
> > Nowadays all disk-arrays make online LUN extension a breeze but
> > unfortunately it seems that dm-multipath is still not able to see new size
> > without downtime:
> > http://www.redhat.com/archives/dm-devel/2007-August/msg00205.html
> > Look also at this recent thread on RHEL5 mailing-list where you can find
> > also a post from a Red Hat representative:
> > http://www.redhat.com/archives/rhelv5-list/2008-July/msg00267.html
> >
> > Sure, you can just add a new LUN, pvcreate and vgextend but it is not a
> > viable solution because it causes LUN proliferation.
> >
> > Sincerely, I'm still subscribed to this mailing-list only to see if someone
> > solve this SHAME!
> > It's a feature that Linux really needs.
> >
> > Hope someone pick this cry of pain!
> >
>
> Thanks for the reply.
>
> Does someone know what's the actual problem in this? meaning why it hasn't
> been done yet..
It has to do with the block layer not using the new size value while there
are openers.
Andrew submitted a patch series (url below) a while ago to try and address
this issue, but I do not know the status. I added Andrew to the cc.
http://thread.gmane.org/gmane.linux.scsi/41623
-andmike
--
Michael Anderson
andmike@linux.vnet.ibm.com
next prev parent reply other threads:[~2008-08-06 19:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 12:53 Status of resizing/growing dm-multipath devices on the fly Pasi Kärkkäinen
2008-08-06 13:48 ` Domenico Viggiani
2008-08-06 14:37 ` Pasi Kärkkäinen
2008-08-06 19:36 ` Mike Anderson [this message]
2008-08-06 20:58 ` Andrew Patterson
2008-08-11 10:36 ` Pasi Kärkkäinen
2008-09-05 8:12 ` Pasi Kärkkäinen
2008-08-06 21:46 ` Sharif Nassar
2008-08-07 7:17 ` Domenico Viggiani
2008-08-11 20:18 ` Sharif Nassar
2008-08-07 7:45 ` Pasi Kärkkäinen
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=20080806193602.GA9941@linux.vnet.ibm.com \
--to=andmike@linux.vnet.ibm.com \
--cc=andrew.patterson@hp.com \
--cc=dm-devel@redhat.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.