- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- device-mapper-multipath
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-19-2006 05:19 PM
тАО08-19-2006 05:19 PM
device-mapper-multipath
(Kernel 2.6.9-22ELsmp)
I have executed the "multipath -v2" command and it generates and shows grouped multipathed devices.
But in several articules I have seen that it should generates a "/dev/disk/by-name/WWID" block devices, but I only get a "/dev/dm-X", "/dev/mapper/WWID" and "/dev/mapper/dm-XpY" block devices; and this generated devices are lost after reboot.
"/dev/dm-X", and "/dev/mapper/WWID" block devices are created after I run again the "multipath -v2" command. And "/dev/mapper/dm-XpY" block devices are created after I run the "kpartx -a /dev/dm-X" command.
Any idea about my case?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-19-2006 10:42 PM
тАО08-19-2006 10:42 PM
Re: device-mapper-multipath
Go to /usr/share/doc/device-mapper-multipath-
There are specific initial setup instructions (Multipath-usage.txt in the above-mentioned directory). Follow these instructions exactly.
Note that some of the documentation in this directory is directly from the "generic" multipath-tools source package, and does *not* refer specifically to RHEL 4 unless it explicitly says so.
You should get your multipath devices as /dev/mapper/mpath*, and symlinks to them as /dev/mpath/mpath*.
The "/dev/disk/by-name/WWID" style of naming seems to be achievable when the multipath tools and udev are configured to work together. Apparently this integration was not yet done when RHEL 4 configuration was frozen for release. At that point, the device-mapper-multipath seems to have been quite recent development and not very well documented. Any documentation written later is likely to refer to the newer (much changed) versions, unless it is specifically written for RHEL 4.
RHEL 4 has multipath-tools version 0.4.5: the udev integration was done in 0.4.6. Further changes were made in 0.4.7, which is the "latest" version.
The device-mapper-multipath developers' web page has a Change Log which might be useful:
http://christophe.varoqui.free.fr/wiki/wakka.php?wiki=Home
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-20-2006 10:13 AM
тАО08-20-2006 10:13 AM
Re: device-mapper-multipath
The multipathd is started up at startup time of the server. The problem is other configuration.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-20-2006 10:41 AM
тАО08-20-2006 10:41 AM
Re: device-mapper-multipath
Aug 20 17:32:44 rac1 kernel: Device sdaa not ready.
Aug 20 17:32:44 rac1 kernel: Device sdb not ready.
Aug 20 17:32:44 rac1 kernel: Device sdd not ready.
Aug 20 17:32:44 rac1 kernel: Device sdg not ready.
Aug 20 17:32:44 rac1 kernel: Device sdh not ready.
Aug 20 17:32:44 rac1 kernel: Device sdj not ready.
Aug 20 17:32:44 rac1 kernel: Device sdl not ready.
Aug 20 17:32:44 rac1 kernel: Device sdm not ready.
Aug 20 17:32:44 rac1 kernel: Device sdp not ready.
Aug 20 17:32:44 rac1 kernel: Device sdr not ready.
Aug 20 17:32:44 rac1 kernel: Device sdu not ready.
Aug 20 17:32:44 rac1 kernel: Device sdv not ready.
Aug 20 17:32:44 rac1 kernel: Device sdx not ready.
Aug 20 17:32:44 rac1 kernel: Device sdz not ready.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-20-2006 11:11 AM
тАО08-20-2006 11:11 AM
Re: device-mapper-multipath
Make sure that the multipath daemon is automatically loaded at reboot :
grep -i autopath /etc/rc.d/rc.sysinit
find /etc/rc.d -print | grep -i autopath
In your last mesage, it looks like a path have changed or have been lost, then all LUNs seen under that path disappeared and Linux kernel is trying to reconnect to them.
Reboot the system to get a neat situation, then check again that autopath daemon has been automatically loaded.
Good lcuk.
Kodjo
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-20-2006 04:13 PM
тАО08-20-2006 04:13 PM
Re: device-mapper-multipath
grep -i autopath /etc/rc.d/rc.sysinit
find /etc/rc.d -print | grep -i autopath
Returns nothing.
The situation with the messages in /var/log/messages is the same after a reboot.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-20-2006 04:16 PM
тАО08-20-2006 04:16 PM
Re: device-mapper-multipath
# grep -i multipath /etc/rc.d/rc.sysinit
if [ -x /sbin/lvm.static -o -x /sbin/multipath -o -x /sbin/dmraid ]; then
if [ -f /etc/multipath.conf -a -x /sbin/multipath ]; then
modprobe dm-multipath >/dev/null 2>&1
/sbin/multipath -v 0
if [ -x /sbin/multipath ]; then
modprobe dm-multipath >/dev/null 2>&1
/sbin/multipath -v 0
if [ -x /sbin/multipath ]; then
modprobe dm-multipath >/dev/null 2>&1
/sbin/multipath -v 0
# find /etc/rc.d -print | grep -i multipath
/etc/rc.d/rc4.d/S13multipathd
/etc/rc.d/rc3.d/S13multipathd
/etc/rc.d/rc6.d/K87multipathd
/etc/rc.d/rc0.d/K87multipathd
/etc/rc.d/init.d/multipathd
/etc/rc.d/rc2.d/S13multipathd
/etc/rc.d/rc1.d/K87multipathd
/etc/rc.d/rc5.d/S13multipathd
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-21-2006 03:20 AM
тАО08-21-2006 03:20 AM
Re: device-mapper-multipath
# chkconfig --list multipathd
multipathd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
Check if it's currently running;
# service multipathd status
multipathd (pid 3961) is running...
Now, with all that said multipathd deals with path checking and restoration. It has nothing to do with setting up the device files on bootup.
I've never seen the /dev/sdk/by-name/WWID setup, but it is possible by setting up multipath and udev rules correctly (and maybe a little scripting). Generally you will have /dev/mpath/
1. Unless you really want the WWID name (e.g. SEMC_____SYMMETRIX______9903673E9000) you should set up some aliases in /etc/multipath.conf. Here is an example of one of mine;
multipath {
wwid SEMC_____SYMMETRIX______9903673E9000
alias sym3E9mp
}
2. You may need to edit /etc/udev/rules.d/40-multipath.rules if you want to tweak your end-results. The defaults should work in most cases.
To help get more specific I would need to know what storage array you are using and perhaps an example of a WWN.
Thanks,
David
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-21-2006 03:40 AM
тАО08-21-2006 03:40 AM
Re: device-mapper-multipath
The "chkconfig --list multipathd" and "service multipathd status" returns me that the service is correctly started at server start up time.
Eventhough the devices are not created on startup time. I need to run "multipath -v2" and "kpartx -a ..." manually to generate again the devices.
About the name of devices and udev. No more questions about that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-21-2006 03:51 AM
тАО08-21-2006 03:51 AM
Re: device-mapper-multipath
Just put the file in /etc/rc.d/init.d/create_multipath_devices (or whatever you want to call it). Then run 'chkconfig create_multipath_devices on'.
You can just use it as is or roll your own.
David