This discussion is archived
1 2 Previous Next 16 Replies Latest reply: Aug 29, 2013 11:20 PM by user2934299 RSS

multipath -ll command doesn't give any output

984496 Newbie
Currently Being Moderated
Hi all,

I am new to configure storage in multipath. I have configured multipath in a newly installed oracle Linux 6.0 following Linux documentation; however, when I tried to list the multipath using the commands, it doesn’t show any output. I have stop and restart services, reboot the server to no fix. I have also check the LUNs that I can see the storage array's FC target ports from the server as well as the storage admin confirm that they are properly connected. Blew is the output when I used the commands. Please help and let me know if you need more info...

root@server1 ~]# multipath -ll
[root@server1 ~]# <-- no output

[root@server1 ~]# ps -ef |grep multipath
root 2563 2437 0 16:10 pts/0 00:00:00 grep multipath
root 20831 1 0 Jan09 ? 00:00:01 /sbin/multipathd


[root@server1 ~]# multipath -d
create: mpatha (3600508b10010414d5155594e56360008) undef HP,LOGICAL VOLUME
size=137G features='0' hwhandler='0' wp=undef
`-+- policy='round-robin 0' prio=1 status=undef
`- 0:0:0:0 cciss!c0d0 104:0 undef ready running

thank you,
Lou
  • 1. Re: multipath -ll command doesn't give any output
    Dude! Guru
    Currently Being Moderated
    It might be that you did not configure /etc/multipath.conf properly and your devices are blacklisted.

    The following enables the multipath configuration file and starts the multipathd daemon:

    <pre>
    mpathconf enable with_multipathd y
    </pre>

    The following entry, for instance will exclude all /dev/sd devices from multipath:

    <pre>
    blacklist {
    devnode "sd*"
    }
    </pre>

    After you change /etc/multipath.conf you need to reload/restart the multipath daemon

    <pre>
    service multipathd reload
    </pre>
  • 2. Re: multipath -ll command doesn't give any output
    984496 Newbie
    Currently Being Moderated
    Hi Dude,

    Thank you for your fast response. As you have recommended, I have checked the ‘multipath.conf’ file for blacklisted ‘sd*’, as you can see below the blacklist block doesn’t have ‘sd*’ listed or anywhere in the file. I have also run the command but didn’t fix it. Is there anything you can recommend?

    blacklist {
    # wwid 26353900f02796769
    devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
    devnode "^hd[a-z][[0-9]*]"
    device {
    vendor "LSILOGIC"
    }

    # devnode "^cciss!c[0-9]d[0-9]*"
    # device {
    # vendor "HP"
    # product "OPEN-*"
    # }
    }



    [root@server1 ~]# service multipathd stop
    Stopping multipathd daemon: [  OK  ]
    [root@server1 ~]#
    [root@server1 ~]# mpathconf enable with_multipathd y
    Starting multipathd daemon: [  OK  ]
    [root@server1 ~]#

    [root@server1 ~]# multipath -ll
    [root@server1 ~]#
    [root@server1 ~]# service multipathd restart
    ok
    Stopping multipathd daemon: [  OK  ]
    Starting multipathd daemon: [  OK  ]
    [root@server1 ~]#

    [root@server1 ~]# multipath -ll
    [root@server1 ~]#

    thank you,
    Lou
  • 3. Re: multipath -ll command doesn't give any output
    Dude! Guru
    Currently Being Moderated
    What device names are you expecting to see?
  • 4. Re: multipath -ll command doesn't give any output
    BillyVerreynne Oracle ACE
    Currently Being Moderated
    Post the output of the following:
    multipath -F
    multipath -v3
    The 1st command flushes multipath - the next command runs it (doing a device discovery and applying <i>multipath.conf</i>) using verbosity level 3. This should show us what multipath does and why there are no mpath devices.
  • 5. Re: multipath -ll command doesn't give any output
    898553 Newbie
    Currently Being Moderated
    Try running a script similar to:

    #!/bin/bash

    DISKLIST=`ls /sys/block/ | grep -E "(sd[b-z]|sd[a-z][a-z])" | xargs` # this will generate a list of disks on the system excluding sda

    for DISKS in `echo $DISKLIST`
    do
    WWID=`/sbin/scsi_id whitelisted replace-whitespace --device=/dev/$DISKS` # this will get you the WWID for a given disk

    echo $DISKS $WWID
    done
  • 6. Re: multipath -ll command doesn't give any output
    984496 Newbie
    Currently Being Moderated
    Hi All,

    Here is the output that you have requested… thank you for the help

    Lou

    reply to: Dude
    ________________

    Q: What device names are you expecting to see?

    A: Simmilar to the below output:

    [root@oldServer ~]# multipath -ll
    ocr_vote_1 (36001438005decdd10006e00003b30000) dm-0 HP,HSV450
    size=1.0G features='1 queue_if_no_path' hwhandler='0' wp=rw
    |-+- policy='round-robin 0' prio=50 status=active
    | |- 0:0:0:3 sdc 8:32 active ready running
    | |- 0:0:1:3 sdq 65:0 active ready running
    | |- 1:0:0:3 sdbg 67:160 active ready running
    | `- 1:0:1:3 sdbu 68:128 active ready running


    Reply to: Billy Verreynne
    __________________________

    Here is the output. I didn't post the repetitive output for the 'sd*'s

    [root@server1 ~]# multipath -v3
    Jan 14 10:23:24 | ram0: device node name blacklisted
    Jan 14 10:23:24 | ram1: device node name blacklisted
    Jan 14 10:23:24 | ram2: device node name blacklisted
    Jan 14 10:23:24 | ram3: device node name blacklisted
    Jan 14 10:23:24 | ram4: device node name blacklisted
    Jan 14 10:23:24 | ram5: device node name blacklisted
    Jan 14 10:23:24 | ram6: device node name blacklisted
    Jan 14 10:23:24 | ram7: device node name blacklisted
    Jan 14 10:23:24 | ram8: device node name blacklisted
    Jan 14 10:23:24 | ram9: device node name blacklisted
    Jan 14 10:23:24 | ram10: device node name blacklisted
    Jan 14 10:23:24 | ram11: device node name blacklisted
    Jan 14 10:23:24 | ram12: device node name blacklisted
    Jan 14 10:23:24 | ram13: device node name blacklisted
    Jan 14 10:23:24 | ram14: device node name blacklisted
    Jan 14 10:23:24 | ram15: device node name blacklisted
    Jan 14 10:23:24 | loop0: device node name blacklisted
    Jan 14 10:23:24 | loop1: device node name blacklisted
    Jan 14 10:23:24 | loop2: device node name blacklisted
    Jan 14 10:23:24 | loop3: device node name blacklisted
    Jan 14 10:23:24 | loop4: device node name blacklisted
    Jan 14 10:23:24 | loop5: device node name blacklisted
    Jan 14 10:23:24 | loop6: device node name blacklisted
    Jan 14 10:23:24 | loop7: device node name blacklisted
    Jan 14 10:23:24 | cciss!c0d0: not found in pathvec
    Jan 14 10:23:24 | cciss!c0d0: mask = 0x1f
    Jan 14 10:23:24 | cciss!c0d0: dev_t = 104:0
    Jan 14 10:23:24 | cciss!c0d0: size = 286677120
    Jan 14 10:23:24 | cciss!c0d0: subsystem = cciss
    Jan 14 10:23:24 | cciss!c0d0: h:b:t:l = 0:0:0:0
    Jan 14 10:23:24 | cciss!c0d0: vendor = HP
    Jan 14 10:23:24 | cciss!c0d0: product = LOGICAL VOLUME
    Jan 14 10:23:24 | cciss!c0d0: revision = 1.86
    Jan 14 10:23:24 | cciss!c0d0: get_state
    Jan 14 10:23:24 | loading /lib64/multipath/libchecktur.so checker
    Jan 14 10:23:24 | cciss!c0d0: path checker = tur (controller setting)
    Jan 14 10:23:24 | cciss!c0d0: checker timeout = 300000 ms (internal default)
    Jan 14 10:23:24 | cciss!c0d0: state = 3
    Jan 14 10:23:24 | cciss!c0d0: getuid = /lib/udev/scsi_id whitelisted device=/dev/%n (controller setting)
    Jan 14 10:23:24 | cciss!c0d0: uid = 3600508b10010414d5155594e56360008 (callout)
    Jan 14 10:23:24 | cciss!c0d0: prio = const (controller setting)
    Jan 14 10:23:24 | cciss!c0d0: const prio = 1
    Jan 14 10:23:24 | sda: not found in pathvec
    Jan 14 10:23:24 | sda: mask = 0x1f
    Jan 14 10:23:24 | sda: dev_t = 8:0
    Jan 14 10:23:24 | sda: size = 104857600
    Jan 14 10:23:24 | sda: subsystem = scsi
    Jan 14 10:23:24 | sda: vendor = HP
    Jan 14 10:23:24 | sda: product = HSV450
    Jan 14 10:23:24 | sda: rev = 0953
    Jan 14 10:23:24 | sda: h:b:t:l = 0:0:0:1
    Jan 14 10:23:24 | sda: tgt_node_name = 0x50001fe1501ec830
    Jan 14 10:23:24 | sda: serial = PAFURC19SYZ0AB
    Jan 14 10:23:24 | sda: get_state
    Jan 14 10:23:24 | sda: path checker = tur (controller setting)
    Jan 14 10:23:24 | sda: checker timeout = 30000 ms (sysfs setting)
    Jan 14 10:23:24 | sda: state = running
    Jan 14 10:23:24 | sda: state = 3
    Jan 14 10:23:24 | sda: getuid = /sbin/scsi_id -g -u -s /block/%n (controller setting)
    Jan 14 10:23:24 | /sbin/scsi_id exitted with 1
    Jan 14 10:23:24 | error calling out /sbin/scsi_id -g -u -s /block/sda
    Jan 14 10:23:24 | sda: state = running
    Jan 14 10:23:24 | /sbin/scsi_id exitted with 1
    Jan 14 10:23:24 | error calling out /sbin/scsi_id -g -u -s /block/sda
    Jan 14 10:23:24 | loading /lib64/multipath/libprioalua.so prioritizer
    Jan 14 10:23:24 | sda: prio = alua (controller setting)
    Jan 14 10:23:24 | reported target port group is 2
    Jan 14 10:23:24 | aas = 01 [active/non-optimized]
    Jan 14 10:23:24 | sda: alua prio = 10
    Jan 14 10:23:24 | sdb: not found in pathvec
    Jan 14 10:23:24 | sdb: mask = 0x1f
    Jan 14 10:23:24 | sdb: dev_t = 8:16
    Jan 14 10:23:24 | sdb: size = 209715200
    Jan 14 10:23:24 | sdb: subsystem = scsi
    Jan 14 10:23:24 | sdb: vendor = HP
    --
    --
    --
    Jan 14 10:23:26 | sdav: not found in pathvec
    Jan 14 10:23:26 | sdav: mask = 0x1f
    Jan 14 10:23:26 | sdav: dev_t = 66:240
    Jan 14 10:23:26 | sdav: size = 2097152
    Jan 14 10:23:26 | sdav: subsystem = scsi
    Jan 14 10:23:26 | sdav: vendor = HP
    Jan 14 10:23:26 | sdav: product = HSV450
    Jan 14 10:23:26 | sdav: rev = 0953
    Jan 14 10:23:26 | sdav: h:b:t:l = 1:0:3:6
    Jan 14 10:23:26 | sdav: tgt_node_name = 0x50001fe1501ec830
    Jan 14 10:23:26 | sdav: serial = PAFURC19SYZ0AB
    Jan 14 10:23:26 | sdav: get_state
    Jan 14 10:23:26 | sdav: path checker = tur (controller setting)
    Jan 14 10:23:26 | sdav: checker timeout = 30000 ms (sysfs setting)
    Jan 14 10:23:26 | sdav: state = running
    Jan 14 10:23:26 | sdav: state = 3
    Jan 14 10:23:26 | sdav: getuid = /sbin/scsi_id -g -u -s /block/%n (controller setting)
    Jan 14 10:23:26 | /sbin/scsi_id exitted with 1
    Jan 14 10:23:26 | error calling out /sbin/scsi_id -g -u -s /block/sdav
    Jan 14 10:23:26 | sdav: state = running
    Jan 14 10:23:26 | /sbin/scsi_id exitted with 1
    Jan 14 10:23:26 | error calling out /sbin/scsi_id -g -u -s /block/sdav
    Jan 14 10:23:26 | sdav: prio = alua (controller setting)
    Jan 14 10:23:26 | reported target port group is 2
    Jan 14 10:23:26 | aas = 01 [active/non-optimized]
    Jan 14 10:23:26 | sdav: alua prio = 10
    ===== paths list =====
    uuid hcil dev dev_t pri dm_st chk_st v
    3600508b10010414d5155594e56360008 0:0:0:0 cciss!c0d0 104:0 1 undef ready H
    0:0:0:1 sda 8:0 10 undef ready H
    0:0:0:2 sdb 8:16 50 undef ready H
    0:0:0:3 sdc 8:32 10 undef ready H
    0:0:0:4 sdd 8:48 10 undef ready H
    0:0:0:5 sde 8:64 50 undef ready H
    0:0:0:6 sdf 8:80 10 undef ready H
    --
    --

    Jan 14 10:23:26 | Found matching wwid [3600508b10010414d5155594e56360008] in bindings file. Setting alias to mpatha
    Jan 14 10:23:26 | cciss!c0d0: ownership set to mpatha
    Jan 14 10:23:26 | cciss!c0d0: not found in pathvec
    Jan 14 10:23:26 | cciss!c0d0: mask = 0xc
    Jan 14 10:23:26 | cciss!c0d0: get_state
    Jan 14 10:23:26 | cciss!c0d0: state = 3
    Jan 14 10:23:26 | cciss!c0d0: const prio = 1
    Jan 14 10:23:26 | mpatha: pgfailback = -2 (config file default)
    Jan 14 10:23:26 | mpatha: pgpolicy = multibus (controller setting)
    Jan 14 10:23:26 | mpatha: selector = round-robin 0 (controller setting)
    Jan 14 10:23:26 | mpatha: features = 0 (controller setting)
    Jan 14 10:23:26 | mpatha: hwhandler = 0 (controller setting)
    Jan 14 10:23:26 | mpatha: rr_weight = 1 (controller setting)
    Jan 14 10:23:26 | mpatha: minio = 1 rq (controller setting)
    Jan 14 10:23:26 | mpatha: no_path_retry = 12 (controller setting)
    Jan 14 10:23:26 | pg_timeout = NONE (internal default)
    Jan 14 10:23:26 | mpatha: set ACT_CREATE (map does not exist)
    Jan 14 10:23:26 | mpatha: domap (0) failure for create/reload map
    Jan 14 10:23:26 | mpatha: ignoring map


    reply for: Theanswriz42:
    ________________________

    Here is part of the output from the scipt...

    sdaa 36001438005decdd10006e000051c0000
    sdab 36001438005decdd10006e000052c0000
    --
    --
    sdz 36001438005decdd10006e00005200000
  • 7. Re: multipath -ll command doesn't give any output
    898553 Newbie
    Currently Being Moderated
    Those look like WWIDs for an EMC array, is that correct? If so, is this for a CLARiiON or Symmetrix array? If it's a CLARiiON, are you guys setting ALUA?
  • 8. Re: multipath -ll command doesn't give any output
    984496 Newbie
    Currently Being Moderated
    Hi Theanswriz42,

    It is an HP array...

    thank you,
    Lou
  • 9. Re: multipath -ll command doesn't give any output
    898553 Newbie
    Currently Being Moderated
    Would you be able to install sg3_utils and run a 'rescan-scsi-bush.sh -r' ?
  • 10. Re: multipath -ll command doesn't give any output
    BillyVerreynne Oracle ACE
    Currently Being Moderated
    981493 wrote:

    Here is the output. I didn't post the repetitive output for the 'sd*'s
    I want to see why a specific SAN LUN device is not assigned as a multipath device,
    Jan 14 10:23:24 | sdb: not found in pathvec
    Jan 14 10:23:24 | sdb: mask = 0x1f
    Jan 14 10:23:24 | sdb: dev_t = 8:16
    Jan 14 10:23:24 | sdb: size = 209715200
    Jan 14 10:23:24 | sdb: subsystem = scsi
    Jan 14 10:23:24 | sdb: vendor = HP
    This seems to be the first LUN of your HP array. Unfortunately you snipped the remaining messages for this device. However, device sdav seems to be a complete listing:
    Jan 14 10:23:26 | sdav: not found in pathvec
    Jan 14 10:23:26 | sdav: mask = 0x1f
    Jan 14 10:23:26 | sdav: dev_t = 66:240
    Jan 14 10:23:26 | sdav: size = 2097152
    Jan 14 10:23:26 | sdav: subsystem = scsi
    Jan 14 10:23:26 | sdav: vendor = HP
    Jan 14 10:23:26 | sdav: product = HSV450
    Jan 14 10:23:26 | sdav: rev = 0953
    Jan 14 10:23:26 | sdav: h:b:t:l = 1:0:3:6
    Jan 14 10:23:26 | sdav: tgt_node_name = 0x50001fe1501ec830
    Jan 14 10:23:26 | sdav: serial = PAFURC19SYZ0AB
    Jan 14 10:23:26 | sdav: get_state
    Jan 14 10:23:26 | sdav: path checker = tur (controller setting)
    Jan 14 10:23:26 | sdav: checker timeout = 30000 ms (sysfs setting)
    Jan 14 10:23:26 | sdav: state = running
    Jan 14 10:23:26 | sdav: state = 3
    Jan 14 10:23:26 | sdav: getuid = /sbin/scsi_id -g -u -s /block/%n (controller setting)
    Jan 14 10:23:26 | /sbin/scsi_id exitted with 1
    Jan 14 10:23:26 | error calling out /sbin/scsi_id -g -u -s /block/sdav
    And that is the error it seems. Multipath attempts to identify the device via its WWID - and this fails. With that failing, it is unable to uniquely identify devices and determine which scsi devices are different paths to the same SAN LUN.

    Run the following commands as root and post the output:
    /sbin/scsi_id -g -u -s /block/sdav; echo $?
    /sbin/scsi_id -p 0x80 -g -u -s /block/sdav; echo $?
    Will be interesting to see why the 1st one fails or supply a non-zero exit code. I expect the 2nd command to work.

    Next, you'll need to configure what multipath uses, and how, for your SAN/storage array. Edit +/etc/multipath.conf+.

    Look for a devices entry. Is it commented out? What you want to do is have an entry along the following lines that recognises your storage array model and configure multipath for it. E.g.
    devices {
           device {
                   vendor                  "HP"
                   product                 "HSV450"
                   getuid_callout          "/sbin/scsi_id -p 0x80 -g -u -s /block/%n"
                   features                "0"
                   hardware_handler        "0"
                   path_selector           "round-robin 0"
                   path_grouping_policy    multibus
                   rr_weight               uniform
                   no_path_retry           12
                   rr_min_io               1000
                   path_checker            directio
                   prio                    const
           }
    }
    I'm not sure what these parameters should be for your HP HSV450 storage array. I've set getuid_callout to the 2nd method for generating a WWID - assuming that it works better than the existing method.

    Have a look at the HP documents/support site for details on recommended multipath settings - EMC has such recommendations and I suspect HP would have too.

    Last comment - blacklist local devices. All of them. Then use the getuid_callout command manually via root for each LUN device. Get the WWID. Configure that WWID in +/etc/multipath.conf+. Explicitly dealing with configuration is my preference - I dislike (and distrust) systems where such configurations are left to be implicitly done. There are too many variations and shades of differences to think this is a robust approach IMO.
  • 11. Re: multipath -ll command doesn't give any output
    984496 Newbie
    Currently Being Moderated
    Hi Billy,

    Sorry for not responding on time... Below is the output of the command you want me to run. I did not do any of the other recommendation since the output doesn't seem correct. I am also researching on HP site

    thank you for your help,
    Lou


    root@server1 ~]# /sbin/scsi_id -g -u -s /block/sdav; echo $?
    /sbin/scsi_id: invalid option -- 's'
    1
    [root@server1 ~]#
    [root@server1 ~]# /sbin/scsi_id -p 0x80 -g -u -s /block/sdav; echo $?
    /sbin/scsi_id: invalid option -- 's'
    1
    [root@server1 ~]#

    --when i run it without the '-s' option, there is no invalid option error but the result is the same

    [root@server1 ~]# /sbin/scsi_id -p 0x80 -g -u /block/sdav; echo $?
    1
  • 12. Re: multipath -ll command doesn't give any output
    Dude! Guru
    Currently Being Moderated
    The "1" you see from the previous command is just the status report and content of the $? variable, which means the previous command returned an error. Are you sure there are any devices from the SAN available on your system? It seems to me you are not actually seeing any of the HP SAN devices. Multipath manages device paths, but does not provide a driver to enable the SAN devices on your system. What do you see if you type .e.g.:

    fdisk -l | grep Disk
  • 13. Re: multipath -ll command doesn't give any output
    984496 Newbie
    Currently Being Moderated
    Hi Dude

    here is the output...


    [root@server1 etc]# fdisk -l | grep Disk
    Disk /dev/sdb doesn't contain a valid partition table
    Disk /dev/sda doesn't contain a valid partition table
    Disk /dev/sde doesn't contain a valid partition table
    Disk /dev/sdg doesn't contain a valid partition table
    Disk /dev/sdc doesn't contain a valid partition table
    Disk /dev/sdd doesn't contain a valid partition table
    Disk /dev/sdi doesn't contain a valid partition table
    Disk /dev/sdh doesn't contain a valid partition table
    Disk /dev/sdj doesn't contain a valid partition table
    Disk /dev/sdf doesn't contain a valid partition table
    Disk /dev/sdk doesn't contain a valid partition table
    Disk /dev/cciss/c0d0: 146.8 GB, 146778685440 bytes
    Disk identifier: 0x0007e103
    Disk /dev/sdb: 107.4 GB, 107374182400 bytes
    Disk identifier: 0x00000000
    Disk /dev/sda: 53.7 GB, 53687091200 bytes
    Disk identifier: 0x00000000
    Disk /dev/sde: 1073 MB, 1073741824 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdg: 53.7 GB, 53687091200 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdc: 161.1 GB, 161061273600 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdd: 1073 MB, 1073741824 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdi: 161.1 GB, 161061273600 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdh: 107.4 GB, 107374182400 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdj: 1073 MB, 1073741824 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdf: 1073 MB, 1073741824 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdk: 1073 MB, 1073741824 bytes
    Disk /dev/sdl doesn't contain a valid partition table
    Disk /dev/sdm doesn't contain a valid partition table
    Disk /dev/sdo doesn't contain a valid partition table
    Disk /dev/sdp doesn't contain a valid partition table
    Disk /dev/sdn doesn't contain a valid partition table
    Disk /dev/sdq doesn't contain a valid partition table
    Disk /dev/sdr doesn't contain a valid partition table
    Disk /dev/sds doesn't contain a valid partition table
    Disk /dev/sdt doesn't contain a valid partition table
    Disk /dev/sdu doesn't contain a valid partition table
    Disk /dev/sdw doesn't contain a valid partition table
    Disk /dev/sdx doesn't contain a valid partition table
    Disk /dev/sdz doesn't contain a valid partition table
    Disk /dev/sdv doesn't contain a valid partition table
    Disk /dev/sdy doesn't contain a valid partition table
    Disk identifier: 0x00000000
    Disk /dev/sdl: 1073 MB, 1073741824 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdm: 53.7 GB, 53687091200 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdo: 161.1 GB, 161061273600 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdp: 1073 MB, 1073741824 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdn: 107.4 GB, 107374182400 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdq: 1073 MB, 1073741824 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdr: 1073 MB, 1073741824 bytes
    Disk identifier: 0x00000000
    Disk /dev/sds: 53.7 GB, 53687091200 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdt: 107.4 GB, 107374182400 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdu: 161.1 GB, 161061273600 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdw: 1073 MB, 1073741824 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdx: 1073 MB, 1073741824 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdz: 1073 MB, 1073741824 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdv: 53.7 GB, 53687091200 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdy: 107.4 GB, 107374182400 bytes
    Disk /dev/sdaa doesn't contain a valid partition table
    Disk /dev/sdae doesn't contain a valid partition table
    Disk /dev/sdaf doesn't contain a valid partition table
    Disk /dev/sdag doesn't contain a valid partition table
    Disk /dev/sdah doesn't contain a valid partition table
    Disk /dev/sdai doesn't contain a valid partition table
    Disk /dev/sdak doesn't contain a valid partition table
    Disk /dev/sdal doesn't contain a valid partition table
    Disk /dev/sdam doesn't contain a valid partition table
    Disk /dev/sdaj doesn't contain a valid partition table
    Disk /dev/sdan doesn't contain a valid partition table
    Disk /dev/sdap doesn't contain a valid partition table
    Disk /dev/sdao doesn't contain a valid partition table
    Disk /dev/sdaq doesn't contain a valid partition table
    Disk /dev/sdar doesn't contain a valid partition table
    Disk /dev/sdas doesn't contain a valid partition table
    Disk identifier: 0x00000000
    Disk /dev/sdaa: 161.1 GB, 161061273600 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdae: 53.7 GB, 53687091200 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdaf: 107.4 GB, 107374182400 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdag: 161.1 GB, 161061273600 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdah: 1073 MB, 1073741824 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdai: 1073 MB, 1073741824 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdak: 53.7 GB, 53687091200 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdal: 107.4 GB, 107374182400 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdam: 161.1 GB, 161061273600 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdaj: 1073 MB, 1073741824 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdan: 1073 MB, 1073741824 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdap: 1073 MB, 1073741824 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdao: 1073 MB, 1073741824 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdaq: 53.7 GB, 53687091200 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdar: 107.4 GB, 107374182400 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdat doesn't contain a valid partition table
    Disk /dev/sdau doesn't contain a valid partition table
    Disk /dev/sdav doesn't contain a valid partition table
    Disk /dev/sdab doesn't contain a valid partition table
    Disk /dev/sdac doesn't contain a valid partition table
    Disk /dev/sdad doesn't contain a valid partition table
    Disk /dev/sdas: 161.1 GB, 161061273600 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdat: 1073 MB, 1073741824 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdau: 1073 MB, 1073741824 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdav: 1073 MB, 1073741824 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdab: 1073 MB, 1073741824 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdac: 1073 MB, 1073741824 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdad: 1073 MB, 1073741824 bytes
    Disk identifier: 0x00000000


    thank you,
    Lou
  • 14. Re: multipath -ll command doesn't give any output
    Dude! Guru
    Currently Being Moderated
    What happens if you login as root and cut and paste the following exactly as shown to the system command prompt. It should create a new multipath.conf file.

    <pre>
    cd /etc
    mv -f multipath.conf multipath.old
    cat > multipath.conf <<EOF
    defaults {
    user_friendly_names yes
    }

    devices {
    device { 
    vendor "(COMPAQ|HP)"
    product "HSV1[01]1|HSV2[01]0|HSV300|HSV4[05]0"
    getuid_callout "/lib/udev/scsi_id --whitelisted --device=/dev/%n"
    features "0"
    hardware_handler "0"
    path_selector "round-robin 0"
    path_grouping_policy group_by_prio
    failback immediate
    rr_weight uniform
    no_path_retry 12
    rr_min_io 1000
    path_checker tur
    prio alua
    }
    }

    #blacklist {
    # devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
    # devnode "^hd[a-z]"
    # devnode "^dcssblk[0-9]*"
    #}
    EOF
    </pre>

    Then type the following:

    <pre>
    service multipathd reload
    multipath -ll
    </pre>

    In case you wonder how I got this information, it is taken from /usr/share/doc/device-mapper-multipath-0.4.9/multipath.conf.defaults
1 2 Previous Next

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points