From: "S. J. van Harmelen" <svh@dds.nl>
To: device-mapper development <dm-devel@redhat.com>
Subject: RE: Reloading multipathd?
Date: Wed, 07 Nov 2007 16:18:47 +0100 [thread overview]
Message-ID: <1194448727.6012.18.camel@sanderbal> (raw)
In-Reply-To: <940B4FF1F5958E4F96FC83C055A2F2611B8B8C@exch-2003.incipient.waltham>
On Wed, 2007-11-07 at 08:33 -0500, Paul Cote wrote:
> Did you do a rescan so that the O/S "sees" the new LUN?
Nope... Could you tell me how to do that? And does a rescan have any
effect on already active LUN's?
> If so; simply do
> a multipath -v2 to build the new path list.
>
> -----Original Message-----
> From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
> On Behalf Of S. J. van Harmelen
> Sent: Wednesday, November 07, 2007 8:08 AM
> To: device-mapper development
> Subject: [dm-devel] Reloading multipathd?
>
> Hi...
>
> I just added another LUN on our storage (MD3000). But now that I run
> multipath -ll I don't see the new LUN.
>
> Do I need to reload something (like /etc/init.d/multipath-tools reload
> maybe)? And if so, can I do this without it interrupting the
> connectivity of the other (production) LUN's?
>
> Sander
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2007-11-07 15:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 13:07 Reloading multipathd? S. J. van Harmelen
2007-11-07 13:33 ` Paul Cote
2007-11-07 15:18 ` S. J. van Harmelen [this message]
2007-11-07 15:44 ` Domenico Viggiani
2007-11-07 16:01 ` S. J. van Harmelen
2007-11-07 16:55 ` malahal
2007-11-07 23:55 ` Paul Cote
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=1194448727.6012.18.camel@sanderbal \
--to=svh@dds.nl \
--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.