From: malahal@us.ibm.com
To: dm-devel@redhat.com
Subject: Re: Multipath and getuid_callout issues withHPXP1024disk array
Date: Wed, 30 Jan 2008 15:33:13 -0800 [thread overview]
Message-ID: <20080130233313.GA9525@us.ibm.com> (raw)
In-Reply-To: <2F1F44D192D1284BAA298E48C1B2A4F90234F150@exchmail03.ncogroup.com>
Greene, Rick [rick.greene@ncogroup.com] wrote:
> create: mpath0 (05:83)
> [size=13 GB][features="0"][hwhandler="0"]
> \_ round-robin 0
> \_ 1:0:0:0 sda 8:0 [ready]
> \_ round-robin 0
> \_ 2:0:0:0 sde 8:64 [ready]
The above out displays two states for me. Maybe your version only
displays one.
> 1) does the actual WWID need to be in the "uid" value that multipath
> gets from the callout, or is any value that is unique to the disk good
> enough?
I think, it can be anything. Doesn't need to match actual WWID.
> 2) what is the character limit to the return value from the
> getuid_callout?
Old versions had it as 64 (63 actual chars) and the latest code has it
set to 128 (maybe 127 real chars)
> 3) is there a specific format that multipath is looking at for parsing
> the info in the uid value (such as vendor, model, type, serial number,
> etc), or is the unique disk identifier all that is needed?
As far as I know, it doesn't parse anything inside WWID. Make sure you
don't have any blanks in the WWID as the bindings file parser will have
trouble if you do have.
next prev parent reply other threads:[~2008-01-30 23:33 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-29 20:56 Multipath and getuid_callout issues with HP XP1024 disk array Greene, Rick
2008-01-29 22:18 ` malahal
2008-01-30 12:45 ` Multipath and getuid_callout issues with HP XP1024disk array Greene, Rick
2008-01-30 18:50 ` malahal
2008-01-30 18:56 ` Multipath and getuid_callout issues with HPXP1024disk array Greene, Rick
2008-01-30 20:11 ` malahal
2008-01-30 20:21 ` Multipath and getuid_callout issues withHPXP1024disk array Greene, Rick
2008-01-30 23:33 ` malahal [this message]
2008-01-31 12:30 ` Multipath and getuid_callout issueswithHPXP1024disk array Greene, Rick
2008-01-31 18:32 ` malahal
2008-01-31 19:05 ` Multipath and getuid_callout issueswithHPXP1024diskarray Greene, Rick
2008-01-31 20:20 ` Multipath not rebuilding correctly on reboot Greene, Rick
2008-01-31 20:21 ` Greene, Rick
2008-02-12 12:16 ` Greene, Rick
2008-02-12 17:42 ` Pradipmaya Maharana
2008-02-12 18:00 ` Greene, Rick
2008-02-12 22:22 ` Benjamin Marzinski
2008-02-14 18:40 ` Greene, Rick
2008-02-15 19:25 ` Benjamin Marzinski
2008-02-17 7:47 ` malahal
2008-02-18 12:10 ` Greene, Rick
2008-02-18 22:20 ` malahal
2008-02-19 12:21 ` Greene, Rick
2008-02-19 17:21 ` Benjamin Marzinski
2008-01-30 22:32 ` HPDMmultipath-tools-3.0.0.xxx with HP XP12000 diskarray Hagmann, Michael
2008-02-04 15:35 ` Balasubramanian, Vijayakumar (STSD)
2008-02-05 9:31 ` Multipath and getuid_callout issues with HPXP1024diskarray Balasubramanian, Vijayakumar (STSD)
2008-02-05 12:21 ` Multipath and getuid_callout issues withHPXP1024diskarray Greene, Rick
2008-02-07 8:39 ` Multipath and getuid_callout issues with HPXP1024disk array Luca Berra
2008-02-07 12:27 ` Multipath and getuid_callout issues with HPXP1024diskarray Greene, Rick
2008-02-07 19:53 ` malahal
2008-02-07 20:05 ` Multipath and getuid_callout issues withHPXP1024diskarray Greene, Rick
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=20080130233313.GA9525@us.ibm.com \
--to=malahal@us.ibm.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.