You should be able to set them up in /etc/multipath.conf

I had issues mounting the filesystems across reboots on an xSeries.
 Red Hat recommended using the /dev/mapper/ as opposed to /dev/mpath##

[ . . . snip from /etc/fstab . . . ]

/dev/mapper/LnP          /LnP_FTP                ext3 acl         1 2
/dev/mapper/100GBno1     /ftpdata2               ext3 acl         1 2
# this is the 16GB LUN Slice below
/dev/mapper/16GBno1      /DigMedNetPgm           ext3 acl         1 2

Seems that there was NO consistency as to how multipath would select path 
numbers. I would always get dropped into maintenance mode
This recommendation fixed my issues since changing fstab to 
/dev/mapper/####



Emmett O'Grady 
Mercedes-Benz USA, LLC. 





[email protected] 
Sent by: [email protected]
10/05/2010 01:45 PM
Please respond to
[email protected]


To
[email protected]
cc

Subject
Re: Question about multipathing on zDebian (Lenny)







Mark,

  I am not familiar with Debian, but if this was a SUSE or REDHAT 
instance,
I would say you need to run mkinitrd and zipl before your reboot.


John





From:       "Wiggins, Mark" <[email protected]>
To:         [email protected]
Date:       10/05/2010 01:37 PM
Subject:    Question about multipathing on zDebian (Lenny)
Sent by:    Linux on 390 Port <[email protected]>



I hate to come and ask what I know is going to be a simple answer, but 
I've
beat my head against the wall for long enough. I'm trying to add some
multipath'd devices to a Debian(Lenny)  instance. I can get the devices
configured properly,


mpath1 (360050768019281af7000000000000153) dm-1 IBM     ,2145

[size=3.7G][features=0][hwhandler=0]

\_ round-robin 0 [prio=0][active]

 \_ 0:0:0:32 sde 8:64  [active][undef]

 \_ 0:0:1:32 sdf 8:80  [active][undef]

 \_ 1:0:0:32 sdg 8:96  [active][undef]

 \_ 1:0:1:32 sdh 8:112 [active][undef]

mpath0 (360050768019281af7000000000000152) dm-0 IBM     ,2145

[size=3.7G][features=0][hwhandler=0]

\_ round-robin 0 [prio=0][active]

 \_ 0:0:0:31 sda 8:0   [active][undef]

 \_ 0:0:1:31 sdb 8:16  [active][undef]

 \_ 1:0:0:31 sdc 8:32  [active][undef]
 \_ 1:0:1:31 sdd 8:48  [active][undef]

I just can't get these definitions to hold across a reboot. I've tried
creating /etc/sysconfig/hardware/config-ccw-0.0.a200
files,/usr/share/initramfs-tools/hooks/multipath_hook file, zipl commands,
update-initramfs commands, etc., but I haven't found what it takes to make
these definitions hold across a reboot. What am I missing besides writing
some kind of a script that has to run after every reboot?

Mark Wiggins
University of Connecticut

My /etc/sysconfig/hardware/config-ccw-0.0.a200 looks like this,

#!/bin/sh

#

# hwcfg-zfcp-bus-ccw-0.0.a200

#

# Configuration for the zfcp adapter at CCW ID 0.0.a200

#

STARTMODE="auto"

MODULE="zfcp"

MODULE_OPTIONS=""

# Scripts to be called for the various events.

# If called manually the event is set to 'up'.

SCRIPTUP="hwup-ccw"

SCRIPTUP_ccw="hwup-ccw"

SCRIPTUP_scsi_host="hwup-zfcp"

SCRIPTDOWN="hwdown-scsi"

SCRIPTDOWN_scsi="hwdown-zfcp"

# Configured zfcp disks

ZFCP_LUNS="0x50050768014035ee:0x001f000000000000"

ZFCP_LUNS="0x50050768014035d9:0x001f000000000000"

ZFCP_LUNS="0x50050768014035ee:0x0020000000000000"

ZFCP_LUNS="0x50050768014035d9:0x0020000000000000"



----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or 
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/




If you are not the intended addressee, please inform us immediately that you 
have received this e-mail in error, and delete it. We thank you for your 
cooperation.  

<<image/gif>>

Reply via email to