From: "Jun'ichi Nomura" <j-nomura@ce.jp.nec.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Resizing multipath maps: reload ioctl failed: Invalid argument
Date: Mon, 27 Aug 2007 11:25:59 -0400 [thread overview]
Message-ID: <46D2ED07.2080003@ce.jp.nec.com> (raw)
In-Reply-To: <46D2CB7F.80900@linpro.no>
Hi,
Tore Anderson wrote:
> Hi. I'm trying to resize multipath maps, but there appears to be
> something wrong with the ioctl call... I resized the "www" volume on
> the storage array from 25GB to 45GB, and attempted to reload it on the
> host, which is running 2.6.23-rc3 and multipath-tools 0.4.7. It
> resulted in the following:
It's due to kernel device-mapper restriction.
multipath-tools uses no_flush suspend of device-mapper device
to save I/O errors in all-paths-down case.
(Without the option, device-mapper needs to flush all pending I/Os,
that will result in I/O errors if there is no working path.)
For no_flush suspend, resizing is disabled because of known dead-lock:
it requires a lock that can be kept hold until the pending I/Os
are flushed.
> Ultimately I found no other way to make this work but to umount the
> file system, then run "multipath -f www; multipath", which kind of
> defeated the point of fancy online resizing support in the file system
> and storage array since I need downtime to do it. Is there any other
> way to make online resizing work?
A workaround for it would be using modified multipath-tools which doesn't
use no_noflush.
Thanks,
--
Jun'ichi Nomura, NEC Corporation of America
next prev parent reply other threads:[~2007-08-27 15:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 13:02 Resizing multipath maps: reload ioctl failed: Invalid argument Tore Anderson
2007-08-27 15:25 ` Jun'ichi Nomura [this message]
2007-08-27 18:47 ` Tore Anderson
2007-08-27 20:29 ` Jun'ichi Nomura
[not found] ` <46D33FA6.5000304@linpro.no>
2007-08-27 22:44 ` Jun'ichi Nomura
-- strict thread matches above, loose matches on Subject: below --
2007-10-24 14:17 Domenico Viggiani
2007-10-24 15:50 ` Aaron Bergstralh
2007-10-24 21:10 ` Jun'ichi Nomura
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=46D2ED07.2080003@ce.jp.nec.com \
--to=j-nomura@ce.jp.nec.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.