Re: [PATCH 0/6] detect online disk resize

From: Andrew Patterson
Date: Fri Sep 05 2008 - 11:15:28 EST


On Fri, 2008-09-05 at 11:21 +0300, Pasi KÃrkkÃinen wrote:
> > 1. For SCSI devices do:
> >
> > # echo 1 > /sys/class/scsi_device/<device>/device/rescan
> >
> > or
> >
> > # blockdev --rereadpt <device file>
> >
> > 2. Other devices (not device mapper)
> >
> > # blockdev --rereadpt <device file>
> >
> > I have tested this patch on SCSI and SmartArray (cciss)
> > devices. Device mapper still does not recognize device size changes
> > until the device is restarted.
> >
>
> Hello and thanks for the patch!
>
> How about device mapper.. what's needed to make it detect/support online resizes?
> I'm specificly interested in online resizing (growing) dm-multipath devices..
>

Yes, it would be nice if this patchset worked here too. It currently
does not.

> Basicly I'd like to have LVM PV on dm-multipath device.. so first I need to
> get the actual disks resized, then dm-multipath device, and finally run pvresize.
>

I did some testing with multipath here. I could get it working by
shutting down the devices, resizing all the underlying paths using the
above methods, restarting the devices, then running pvresize. This
method does not help much given that most users cannot realistically
shutdown a device. This patch series works fine with standard LVM/dm,
i.e., resize using one of the above methods, then run pvresize.

I was planning on looking into dm-multipath in the near future. Mike
Anderson has done some work in this area in the past.

> I know dm-multipath part can be done atm using this (hacky) method:
> https://www.redhat.com/archives/dm-devel/2008-August/msg00033.html
>

This is indeed ugly. It looks like they are pulling the paths out of
the device, resizing them, and then adding them back in.

> -- Pasi


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/