All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy <genanr@emsphone.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: device mapper and resizing devices
Date: Tue, 1 Mar 2005 16:22:45 -0600	[thread overview]
Message-ID: <20050301222245.GA28834@thumper2> (raw)
In-Reply-To: <1109715643.21776.1.camel@zezette>

On Tue, Mar 01, 2005 at 11:20:43PM +0100, christophe varoqui wrote:
> On Tue, 2005-03-01 at 15:03 -0600, Andy wrote:
> >I am using dm-multipath on non-partitioned (xfs) devices on a SAN.  If I
> >resize the device, and rescan my path devices (i.e rescan /dev/sda,
> >/dev/sdb, /dev/sdc,/dev/sdd (all the same path)) the kernel sees the new
> >size of the individual devices, but the /sys/block/dm-0 device is still the
> >old size.  I believe this is the reason why I cannot grow my xfs filesystem
> >without doing a reboot so that the dm device will have the new size. I'd
> >like to avoid unmounting and rebooting to resize the device.  I haven't
> >played with lvm enough to feel comfortable using it.  Is there any way to
> >get the dm device to be the proper size, or is this a bug, or a feature that
> >needs further discussion?
> >
> 
> Runing "multipath" again, after rescans, should pick up the size change
> and adjust the device map.
> 
multipath does, and prints the new size, but it is unable to add the target
to the dm table because dev_size in device-mapper is still the smaller size
and I get the "device x:yy too small for target" message
(/sys/block/dm-x/size still shows the old size, even when everything else
has the new size).

Andy

 

  reply	other threads:[~2005-03-01 22:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-01 21:03 device mapper and resizing devices Andy
2005-03-01 21:11 ` Arthur Bergman
2005-03-01 22:20 ` christophe varoqui
2005-03-01 22:22   ` Andy [this message]
2005-03-02  0:03   ` Arthur Bergman

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=20050301222245.GA28834@thumper2 \
    --to=genanr@emsphone.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.