From: Sajesh Singh <ssingh@amnh.org>
To: dm-devel@redhat.com, bmarzins@redhat.com
Subject: Re: Pathvec messages
Date: Tue, 29 Jul 2008 13:34:47 -0400 [thread overview]
Message-ID: <488F54B7.6030600@amnh.org> (raw)
In-Reply-To: <20080729170455.GE30728@ether.msp.redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 1304 bytes --]
________________________________________________________
Sajesh Singh
Senior Systems Administrator
American Museum of Natural History
Central Park West at 79th Street
New York, NY 10024
(O) (212) 313-7263
(C) (917) 577-9195
(E) ssingh@amnh.org
Benjamin Marzinski wrote:
> On Tue, Jul 29, 2008 at 12:51:42PM -0400, Sajesh Singh wrote:
>
>> Whenever I run the multipath -v3 command on a EL 5 server I see the
>> following line in the output for each device.
>>
>> sdc: not found in pathvec
>>
>
> This simply means that the device is not already stored in multipath's
> in memory list of discovered paths. It's completely normal to see this
> for your all your devices when running the multipath command.
>
> -Ben
>
>
That being said, when does the device make it into the memory list of
discovered paths ?
>> I have seen questions on this before, but no answer as to what this means.
>> Is the message merely information or does the multipath configuration need
>> to be changed?
>>
>> Regards,
>>
>> Sajesh
>>
>> --
>> dm-devel mailing list
>> dm-devel@redhat.com
>> https://www.redhat.com/mailman/listinfo/dm-devel
>>
[-- Attachment #1.2: Type: text/html, Size: 2140 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2008-07-29 17:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 16:51 Pathvec messages Sajesh Singh
2008-07-29 17:04 ` Benjamin Marzinski
2008-07-29 17:34 ` Sajesh Singh [this message]
2008-07-29 19:07 ` Benjamin Marzinski
2008-07-29 19:43 ` Sajesh Singh
2008-07-30 17:37 ` Benjamin Marzinski
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=488F54B7.6030600@amnh.org \
--to=ssingh@amnh.org \
--cc=bmarzins@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox