FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Device-mapper Development

 
 
LinkBack Thread Tools
 
Old 02-05-2008, 08:31 AM
"Balasubramanian, Vijayakumar (STSD)"
 
Default Multipath and getuid_callout issues with HPXP1024diskarray

Rick,

scsi_id does give unique id for HP XP array LUNs which can be used by
device mapper. Following is the output that I get on my xp device:
# /sbin/scsi_id -g -u -s /block/sdaq
360060e8005276a000000276a0000030e

Can you verify the LUN presentation/ Host mode settings on the array and
the low level drivers on the host.

Note: If you use XP128/1024, the system modes 140 and 293 must be
switched on, otherwise
the XP array does not respond to a SCSI inquiry to code page 0x83 with a
unique serial number
(scsi_id tool). This prevents the DM Multipath from detecting the
redundant paths.

Hope this helps.

-Vijay


-----Original Message-----
From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
On Behalf Of Greene, Rick
Sent: Thursday, January 31, 2008 12:26 AM
To: device-mapper development
Subject: RE: [dm-devel] Multipath and getuid_callout issues with
HPXP1024diskarray

I've been trying to play with using a different command in the
getuid_callout, but everything I try comes up with "error calling out".
For example, I wrote my own little shell script that pushes out the same
scsi_id string, plus some output from a vendor-supplied disk querying
command, and this is what "multipath -v3" shows for one of the devices
(they all display similar results):

===== path info sda (mask 0x1f) =====
bus = 1
dev_t = 8:0
size = 28452960
vendor = HP
product = OPEN-E
rev = 2114
h:b:t:l = 1:0:0:0
tgt_node_name = 0x50060e80039c5a04
serial = 40026
path checker = readsector0 (internal default) state = 2 getprio =
/bin/true (internal default) prio = 0 getuid = /sbin/xpdisk %n (internal
default) error calling out /sbin/xpdisk sda uid = (callout)

Run manually, it looks like this:
# /sbin/xpdisk sda
0HP_OPEN-E_50060e80039c5a0400000000000000000000e100_05:83

I've tried various things with the script I wrote, including just
spitting out the 05:83 (which is the CU:LDev values from the disk array,
pretty much the most unique disk identifying info I can find)

Not sure what else to do.

Thanks,
Rick

-----Original Message-----
From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
On Behalf Of malahal@us.ibm.com
Sent: Wednesday, January 30, 2008 1:50 PM
To: dm-devel@redhat.com
Subject: Re: [dm-devel] Multipath and getuid_callout issues with
HPXP1024disk array

You have two default sections in your multipath.conf file, but that is
not the problem though. The scsi_id output from each path looks
different, that is why multipath treats them as different LUNs.

Make sure you configure your storage properly or change the default
getuid string that works for your storage.

Thanks, Malahal.

Greene, Rick [rick.greene@ncogroup.com] wrote:
> Ok, some more background first:
>
> System is an HP Proliant DL380 (or maybe DL580?), using Emulex fibre
> channel cards (don't know exact model off-hand).
>
> Running Red Hat Enterprise Linux 4, update 5.
>
> Device-mapper-multipath was version 0.4.5-21, just updated it to
> 0.4.5-27
>
> There are 4 LUNs from an HP XP1024 disk array, each pathed to be
visible
> on each fibre channel. LUN type is OPEN-E.
>
> Multipath now seems to accept the longer string returned by scsi_id,
but
> it doesn't seem able to tell that certain disks are the same.
>
> Attached is the multipath.conf file I'm using and the output from
> "multipath -v3". If the attachments don't come through, I'll send
> separate emails with just the contents for each file.
>
> Any aide gladly received, I'm in over my head on this one.
>
> Thanks,
> Rick
>
>
> -----Original Message-----
> From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
> On Behalf Of malahal@us.ibm.com
> Sent: Tuesday, January 29, 2008 5:19 PM
> To: dm-devel@redhat.com
> Subject: Re: [dm-devel] Multipath and getuid_callout issues with HP
> XP1024disk array
>
> Greene, Rick [rick.greene@ncogroup.com] wrote:
> > I've done what I can to try to understand how all this works, but
I
> keep
> > getting "error calling out /sbin/scsi_id -g -u -s /block/sda"
when
> I run
> > the command "multipath -v2"
> >
> >
> >
> > I've tried a number of different things in the
/etc/multipath.conf
> file,
> > but keep coming back to this same error. If I run the command
> manually I
> > get the following:
> >
> >
> >
> > # /sbin/scsi_id -g -u -s /block/sda
> >
> > 0HP______OPEN-E__________50060e80039c5a0400000000000000000000e10 0
> >
> >
> >
> > What's missing? Any help greatly appreciated.
>
> You are not missing anything. The device id is too big to fit in
> multipath tools allocated memory. The program incorrectly prints that
> there is a problem while executing /sbin/scsi_id but in fact the
problem
> lies in the program itself. You may have some old version of multipath

> tools. WWID_SIZE was set to 64 bytes and that is small for your
device.
> Get the latest version where that macro is set to 128 or so.
>
> Hope that helps!
>
> --Malahal.
>
> --
> 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

--
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

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
 
Old 02-07-2008, 11:27 AM
"Greene, Rick"
 
Default Multipath and getuid_callout issues with HPXP1024diskarray

I finally got a support call going with HP, and here's the "official"
resolution:

The XP1024 disk array has to be at a certain firmware version for the
required system modes of 140 and 293 to be available to be turned on.
Additionally, HP states that the configuration is only "blessed" for
certain versions of Red Hat, HBA cards, and drivers. Oh, one other
thing...you have to load their version of DMM, not the standard version
that comes with RedHat or downloading and compiling your own version.
Their version currently doesn't have the patch for the longer strings in
getuid_callout.

By going to www.hp.com and putting in "device mapper multipath" in the
search box, you should find a link to "Device Mapper Multipath
Enablement Kit for HP StorageWorks Disk Arrays Installation and
Reference Guide", a PDF document which details everything. Don't want
to quote it here as it'll likely change over time.

After working with a fairly knowledgeable person at HP, my solution is
to use a custom script that parses output from the unsupported "xpinfo"
command from HP to pull out the CU:LDev value of the devices and feed
that back into multipath.

Works fine, except for an odd issue at reboot times, for which I've got
a separate unanswered query out to this list.

Thanks to Malahal, Vijayakumar Balasubramanian, and Luca Berra for their
responses.

Rick

-----Original Message-----
From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
On Behalf Of Luca Berra
Sent: Thursday, February 07, 2008 3:39 AM
To: dm-devel@redhat.com
Subject: Re: [dm-devel] Multipath and getuid_callout issues with
HPXP1024diskarray

On Wed, Jan 30, 2008 at 01:56:09PM -0500, Greene, Rick wrote:
>I've been trying to play with using a different command in the
>getuid_callout, but everything I try comes up with "error calling out".
>For example, I wrote my own little shell script that pushes out the
same
>scsi_id string, plus some output from a vendor-supplied disk querying
>command, and this is what "multipath -v3" shows for one of the devices
>(they all display similar results):

can you strace the multipath invocation, so maybe we will see if it
really does execute your callout?

I solved a problem similar to yours by using a custom script myself,
about one year ago for a customer using an xp12000, unfortunately i
don't have a copy of the script or of the multipath configuration at
that site.

L.

--
Luca Berra -- bluca@comedia.it
Communication Media & Services S.r.l.
/"
/ ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/

--
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
 
Old 02-07-2008, 06:53 PM
 
Default Multipath and getuid_callout issues with HPXP1024diskarray

Greene, Rick [rick.greene@ncogroup.com] wrote:
> Works fine, except for an odd issue at reboot times, for which I've got
> a separate unanswered query out to this list.

Is it possible that your paths were not ready when multipath tried to
configure your paths as part of the boot process? Will they get
configured correctly when you restart the rc service (multipathd)?
If they get configured correctly when you run 'service multipathd
restart', I would assume that the problem is udev related, and a
udevsettle in the /etc/init.d/multipathd init script may help!

I am out of ideas and just shooting in the dark! :-)

--Malahal.

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
 

Thread Tools




All times are GMT. The time now is 12:08 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org