All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Marzinski <bmarzins@redhat.com>
To: Sajesh Singh <ssingh@amnh.org>
Cc: dm-devel@redhat.com
Subject: Re: Pathvec messages
Date: Wed, 30 Jul 2008 12:37:02 -0500	[thread overview]
Message-ID: <20080730173701.GG30728@ether.msp.redhat.com> (raw)
In-Reply-To: <488F72E4.7020506@amnh.org>

On Tue, Jul 29, 2008 at 03:43:32PM -0400, Sajesh Singh wrote:
>    Benjamin Marzinski wrote:
> 
>  On Tue, Jul 29, 2008 at 01:34:47PM -0400, Sajesh Singh wrote:
> 
> 
> 
>     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 ?
> 
> 
>  Immediately after multipath realizes that it's not there.  In
>  multipathd, which uses the same code, you will see this when multipath
>  first spots a new device.  After that, the device will be list of
>  discovered paths.
> 
>  -Ben
> 
> 
>    So running multipath -v3 multiple times and seeing the output of "not
>    found in pathvec" is merely informational?
> 

Correct.

-Ben
> 
> 
> 
>   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
>   [[1]2]dm-devel@redhat.com
>   [3][2]https://www.redhat.com/mailman/listinfo/dm-devel
> 
> 
>  References
> 
>     Visible links
>     1. [3]mailto:dm-devel@redhat.com
>     2. [4]https://www.redhat.com/mailman/listinfo/dm-devel
> 
> 
> References
> 
>    Visible links
>    1. mailto:2]dm-devel@redhat.com
>    2. https://www.redhat.com/mailman/listinfo/dm-devel
>    3. mailto:dm-devel@redhat.com
>    4. https://www.redhat.com/mailman/listinfo/dm-devel

      reply	other threads:[~2008-07-30 17:37 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
2008-07-29 19:07     ` Benjamin Marzinski
2008-07-29 19:43       ` Sajesh Singh
2008-07-30 17:37         ` Benjamin Marzinski [this message]

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=20080730173701.GG30728@ether.msp.redhat.com \
    --to=bmarzins@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=ssingh@amnh.org \
    /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.