* Multipath setup and rdac questions
@ 2009-02-05 13:58 Christian Røsnes
2009-02-05 15:07 ` Bryn M. Reeves
0 siblings, 1 reply; 15+ messages in thread
From: Christian Røsnes @ 2009-02-05 13:58 UTC (permalink / raw)
To: dm-devel
[-- Attachment #1.1: Type: text/plain, Size: 6333 bytes --]
Hi
I have got a couple of MD3000i with dual controllers,
and two M600e blades connected two both of them.
I've setup multipath, and would appreciate if
someone could tell me whether the setup described
below looks correct, or if you'd do it any
other way.
The reason I'm asking, is that I cannot see any
reference to 'rdac hardware handler' when
I do "multipath -ll".
However, when I change the module controller
ownership one of the LUNs (while copying files to that
particular LUN), the failover seems to work -
the gilr copying continues after the controller switch.
I also see these messages in /var/log/messages when
I change the module controller ownership:
494 [RAIDarray.mpp]MD3000i_A:0:1:0 Cmnd-failed try alt ctrl 1. vcmnd SN
351494
pdev H2:C0:T0:L0 0x05/0x94/0x01 0x08000002 mpp_status:1
Q1: What could be the reason that I'm not using the rdac hwhandler ?
(see output from "multipath -ll" below)
Q2: Is using rdac for this kind of setup preferred ?
Q3: I've created a GPFS filesystem using the /dev/dm-0, /dev/dm-1, etc
device. Is it OK to use the dm-x devices ? I see that there
are other alternatives such as /dev/mapper/mpath<x>.
However, /dev/mapper/mpath<x> is not visible in /proc/partitions
(see below), but the dm-<x> devices are - and the GPFS filesystem complains
when
it cannot see the devices in /proc/partitions.
Q4: Does my setup described here look OK ?
The blades are running:
SLES 10 SP2 (x86-64)
From the MD3000i Dell Resource CD the following rpm was installed:
linuxrdac-09.03.0C06.0030-1dkms
The following modules are running on my blades:
# lsmod | egrep 'rdac|mpp|multi'
dm_rdac 24832 0
dm_multipath 42640 3 dm_rdac,dm_round_robin
dm_mod 80528 26 dm_multipath
mppVhba 145120 24
mppUpper 127436 1 mppVhba
scsi_mod 170936 12 dm_rdac,iscsi_tcp,
libiscsi,
scsi_transport_iscsi,
mptctl,mppVhba,mptsas,
mptscsih,
scsi_transport_sas,
mppUpper,sg,sd_mod
My multipath.conf file contains:
#cat /etc/multipath.conf
defaults {
udev_dir /dev
user_friendly_names yes
}
blacklist {
devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
devnode "^hd[a-z]"
devnode "^sda"
devnode "^sda[0-9]"
device {
vendor DELL
product "PERC|Universal"
}
}
devices {
device {
vendor "DELL"
product "MD3000i"
product_blacklist "Universal Xport"
features "1 queue_if_no_path"
path_grouping_policy group_by_prio
hardware_handler "1 rdac"
path_checker rdac
prio "rdac"
failback immediate
}
}
multipaths {
mulitpath {
device {
vendor DELL
product MD3000i
}
}
}
After changing the multipath.conf I did:
multipath -F
service multipathd restart
Now, if I've do:
# multipath -ll
mpathe (36002219000918b4c00005b6c497e6632) dm-4 DELL,MD Virtual Disk
[size=5.5T][features=0][hwhandler=0]
\_ round-robin 0 [prio=1][active]
\_ 9:0:0:1 sdi 8:128 [active][ready]
mpathd (36002219000918b3300002e6e497e6315) dm-3 DELL,MD Virtual Disk
[size=5.5T][features=0][hwhandler=0]
\_ round-robin 0 [prio=1][active]
\_ 9:0:0:2 sdj 8:144 [active][ready]
mpathc (36002219000918b4c00005b6f497e6695) dm-2 DELL,MD Virtual Disk
[size=5.5T][features=0][hwhandler=0]
\_ round-robin 0 [prio=1][active]
\_ 9:0:0:3 sdk 8:160 [active][ready]
mpathb (36002219000918b3300002e71497e6378) dm-1 DELL,MD Virtual Disk
[size=5.5T][features=0][hwhandler=0]
\_ round-robin 0 [prio=1][active]
\_ 9:0:0:4 sdl 8:176 [active][ready]
mpatha (36002219000918b4c00005b72497e66f3) dm-0 DELL,MD Virtual Disk
[size=5.5T][features=0][hwhandler=0]
\_ round-robin 0 [prio=1][active]
\_ 9:0:0:5 sdm 8:192 [active][ready]
mpathl (36002219000918b3300002e6b497e62a6) dm-11 DELL,MD Virtual Disk
[size=5.5T][features=0][hwhandler=0]
\_ round-robin 0 [prio=1][active]
\_ 9:0:0:0 sdb 8:16 [active][ready]
mpathk (36002219000922cdf000004a4497e53f5) dm-10 DELL,MD Virtual Disk
[size=5.5T][features=0][hwhandler=0]
\_ round-robin 0 [prio=1][active]
\_ 9:0:1:10 sdc 8:32 [active][ready]
mpathj (36002219000918b2e000004b2497e581c) dm-9 DELL,MD Virtual Disk
[size=5.5T][features=0][hwhandler=0]
\_ round-robin 0 [prio=1][active]
\_ 9:0:1:11 sdd 8:48 [active][ready]
mpathi (36002219000922cdf000004a7497e54dd) dm-8 DELL,MD Virtual Disk
[size=5.5T][features=0][hwhandler=0]
\_ round-robin 0 [prio=1][active]
\_ 9:0:1:12 sde 8:64 [active][ready]
mpathh (36002219000918b2e000004b5497e587e) dm-7 DELL,MD Virtual Disk
[size=5.5T][features=0][hwhandler=0]
\_ round-robin 0 [prio=1][active]
\_ 9:0:1:13 sdf 8:80 [active][ready]
mpathg (36002219000922cdf000004aa497e5532) dm-6 DELL,MD Virtual Disk
[size=5.5T][features=0][hwhandler=0]
\_ round-robin 0 [prio=1][active]
\_ 9:0:1:14 sdg 8:96 [active][ready]
mpathf (36002219000918b2e000004b8497e58dc) dm-5 DELL,MD Virtual Disk
[size=5.5T][features=0][hwhandler=0]
\_ round-robin 0 [prio=1][active]
\_ 9:0:1:15 sdh 8:112 [active][ready]
cat /proc/partitions
major minor #blocks name
8 0 71041024 sda
8 1 530113 sda1
8 2 8393962 sda2
8 3 62115322 sda3
8 16 5857419264 sdb
8 32 5857419264 sdc
8 48 5857419264 sdd
8 64 5857419264 sde
8 80 5857419264 sdf
8 96 5857419264 sdg
8 112 5857419264 sdh
8 128 5857419264 sdi
8 144 5857419264 sdj
8 160 5857419264 sdk
8 176 5857419264 sdl
8 192 5857419264 sdm
253 0 5857419264 dm-0
253 1 5857419264 dm-1
253 2 5857419264 dm-2
253 3 5857419264 dm-3
253 4 5857419264 dm-4
253 5 5857419264 dm-5
253 6 5857419264 dm-6
253 7 5857419264 dm-7
253 8 5857419264 dm-8
253 9 5857419264 dm-9
253 10 5857419264 dm-10
253 11 5857419264 dm-11
Thank you
Christian
[-- Attachment #1.2: Type: text/html, Size: 11726 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
^ permalink raw reply [flat|nested] 15+ messages in thread* Re: Multipath setup and rdac questions
2009-02-05 13:58 Multipath setup and rdac questions Christian Røsnes
@ 2009-02-05 15:07 ` Bryn M. Reeves
2009-02-05 17:37 ` Moger, Babu
` (2 more replies)
0 siblings, 3 replies; 15+ messages in thread
From: Bryn M. Reeves @ 2009-02-05 15:07 UTC (permalink / raw)
To: device-mapper development
Christian Røsnes wrote:
> Hi
>
> I have got a couple of MD3000i with dual controllers, and two M600e
> blades connected two both of them.
>
> I've setup multipath, and would appreciate if someone could tell me
> whether the setup described below looks correct, or if you'd do it
> any other way. The reason I'm asking, is that I cannot see any
> reference to 'rdac hardware handler' when I do "multipath -ll".
>
> However, when I change the module controller ownership one of the
> LUNs (while copying files to that particular LUN), the failover
> seems to work - the gilr copying continues after the controller
> switch.
>
> I also see these messages in /var/log/messages when I change the
> module controller ownership:
>
> 494 [RAIDarray.mpp]MD3000i_A:0:1:0 Cmnd-failed try alt ctrl 1.
> vcmnd SN 351494 pdev H2:C0:T0:L0 0x05/0x94/0x01 0x08000002
> mpp_status:1
Don't know where this is coming form. Do you have IBM's MPP
multipathing driver installed? If you are using device-mapper
multipath and multipath tools (the rest of your mail suggests this is
your intention) you should not load the MPP modules.
> Q1: What could be the reason that I'm not using the rdac hwhandler
> ? (see output from "multipath -ll" below)
Your vendor/product details don't seem to match what the array is
reporting.
> Q2: Is using rdac for this kind of setup preferred ?
Yes. It's required for proper failover if you're using device-mapper
multipathing.
> Q3: I've created a GPFS filesystem using the /dev/dm-0, /dev/dm-1,
> etc device. Is it OK to use the dm-x devices ? I see that there are
> other alternatives such as /dev/mapper/mpath<x>.
I always recommend using the /dev/mapper/* entries. These are
guaranteed to exist when the device is created (unlike the
udev-managed symlinks sometimes found in /dev/mpath) and are more
meaningful than the "dm-N" names which are really an internal
device-mapper name for the device.
> However, /dev/mapper/mpath<x> is not visible in /proc/partitions
> (see below), but the dm-<x> devices are - and the GPFS filesystem
> complains it cannot see the devices in /proc/partitions.
It's not meant to be - you'll only see the dm-N names here. That's
what udev refers to as the "kernel name" for the device. The entries
in /dev/mapper are aliases that are intended to be more
useful/meaningful to administrators. Internally they are the same device.
> Q4: Does my setup described here look OK ?
See comments below.
> The blades are running:
>
> SLES 10 SP2 (x86-64)
>
>> From the MD3000i Dell Resource CD the following rpm was
>> installed:
>
> linuxrdac-09.03.0C06.0030-1dkms
No idea what this contains.
> The following modules are running on my blades:
>
> # lsmod | egrep 'rdac|mpp|multi' dm_rdac 24832 0
> dm_multipath 42640 3 dm_rdac,dm_round_robin dm_mod
> 80528 26 dm_multipath
These are the modules needed for device-mapper multipathing.
> mppVhba 145120 24 mppUpper 127436 1
> mppVhba
These are the IBM MPP modules. You should not load these if using
device-mapper for multipathing. If you want to use MPP instead, refer
to the IBM documentation.
> device { vendor DELL product "PERC|Universal" }
Shouldn't be required as you seem to have blacklisted these devices by
device node.
> devices { device { vendor "DELL" product
> "MD3000i"
These don't match the vendor/product details in the multipath output
below.
You should check what the MD3000i reports in sysfs. E.g. for an EMC
clariion device I see:
# cat /sys/block/sdj/device/vendor
DGC
# cat /sys/block/sdj/device/model
RAID 5
And the corresponding entry in multipath.conf is:
vendor "DGC"
product "*"
I suspect from the output below that you want:
vendor "DELL"
product "DELL,MD Virtual Disk"
But check in sysfs.
> multipaths { mulitpath { device { vendor DELL product MD3000i } } }
>
This block does not define anything.
> After changing the multipath.conf I did:
>
> multipath -F service multipathd restart
>
> Now, if I've do:
>
> # multipath -ll mpathe (36002219000918b4c00005b6c497e6632) dm-4
> DELL,MD Virtual Disk [size=5.5T][features=0][hwhandler=0] \_
> round-robin 0 [prio=1][active] \_ 9:0:0:1 sdi 8:128
> [active][ready]
Your settings are being ignored, probably because of a vendor/product
mismatch.
Regards,
Bryn.
^ permalink raw reply [flat|nested] 15+ messages in thread* RE: Multipath setup and rdac questions
2009-02-05 15:07 ` Bryn M. Reeves
@ 2009-02-05 17:37 ` Moger, Babu
2009-02-05 17:44 ` Bryn M. Reeves
2009-02-05 19:13 ` Christian Røsnes
2009-02-05 18:48 ` Christian Røsnes
2009-02-05 18:56 ` Christian Røsnes
2 siblings, 2 replies; 15+ messages in thread
From: Moger, Babu @ 2009-02-05 17:37 UTC (permalink / raw)
To: device-mapper development
Like Bryn said, you cannot have both MPP and device mapper together. MPP will be the first one to load. So it will claim all the devices.
I have modified your multipath.conf file. Please try this one below.
devices {
device {
vendor "DELL"
product "MD3000i"
product_blacklist "Universal Xport"
features "1 queue_if_no_path"
path_grouping_policy group_by_prio
prio_callout "/sbin/mpath_prio_rdac /dev/%n"
getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
hardware_handler "1 rdac"
path_checker rdac
prio "rdac"
failback immediate
}
}
Make sure you have mpath_prio_rdac and scsi_id in sbin directories.
Thanks
Babu Moger
-----Original Message-----
From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com] On Behalf Of Bryn M. Reeves
Sent: Thursday, February 05, 2009 9:08 AM
To: device-mapper development
Subject: Re: [dm-devel] Multipath setup and rdac questions
Christian Røsnes wrote:
> Hi
>
> I have got a couple of MD3000i with dual controllers, and two M600e
> blades connected two both of them.
>
> I've setup multipath, and would appreciate if someone could tell me
> whether the setup described below looks correct, or if you'd do it
> any other way. The reason I'm asking, is that I cannot see any
> reference to 'rdac hardware handler' when I do "multipath -ll".
>
> However, when I change the module controller ownership one of the
> LUNs (while copying files to that particular LUN), the failover
> seems to work - the gilr copying continues after the controller
> switch.
>
> I also see these messages in /var/log/messages when I change the
> module controller ownership:
>
> 494 [RAIDarray.mpp]MD3000i_A:0:1:0 Cmnd-failed try alt ctrl 1.
> vcmnd SN 351494 pdev H2:C0:T0:L0 0x05/0x94/0x01 0x08000002
> mpp_status:1
Don't know where this is coming form. Do you have IBM's MPP
multipathing driver installed? If you are using device-mapper
multipath and multipath tools (the rest of your mail suggests this is
your intention) you should not load the MPP modules.
> Q1: What could be the reason that I'm not using the rdac hwhandler
> ? (see output from "multipath -ll" below)
Your vendor/product details don't seem to match what the array is
reporting.
> Q2: Is using rdac for this kind of setup preferred ?
Yes. It's required for proper failover if you're using device-mapper
multipathing.
> Q3: I've created a GPFS filesystem using the /dev/dm-0, /dev/dm-1,
> etc device. Is it OK to use the dm-x devices ? I see that there are
> other alternatives such as /dev/mapper/mpath<x>.
I always recommend using the /dev/mapper/* entries. These are
guaranteed to exist when the device is created (unlike the
udev-managed symlinks sometimes found in /dev/mpath) and are more
meaningful than the "dm-N" names which are really an internal
device-mapper name for the device.
> However, /dev/mapper/mpath<x> is not visible in /proc/partitions
> (see below), but the dm-<x> devices are - and the GPFS filesystem
> complains it cannot see the devices in /proc/partitions.
It's not meant to be - you'll only see the dm-N names here. That's
what udev refers to as the "kernel name" for the device. The entries
in /dev/mapper are aliases that are intended to be more
useful/meaningful to administrators. Internally they are the same device.
> Q4: Does my setup described here look OK ?
See comments below.
> The blades are running:
>
> SLES 10 SP2 (x86-64)
>
>> From the MD3000i Dell Resource CD the following rpm was
>> installed:
>
> linuxrdac-09.03.0C06.0030-1dkms
No idea what this contains.
> The following modules are running on my blades:
>
> # lsmod | egrep 'rdac|mpp|multi' dm_rdac 24832 0
> dm_multipath 42640 3 dm_rdac,dm_round_robin dm_mod
> 80528 26 dm_multipath
These are the modules needed for device-mapper multipathing.
> mppVhba 145120 24 mppUpper 127436 1
> mppVhba
These are the IBM MPP modules. You should not load these if using
device-mapper for multipathing. If you want to use MPP instead, refer
to the IBM documentation.
> device { vendor DELL product "PERC|Universal" }
Shouldn't be required as you seem to have blacklisted these devices by
device node.
> devices { device { vendor "DELL" product
> "MD3000i"
These don't match the vendor/product details in the multipath output
below.
You should check what the MD3000i reports in sysfs. E.g. for an EMC
clariion device I see:
# cat /sys/block/sdj/device/vendor
DGC
# cat /sys/block/sdj/device/model
RAID 5
And the corresponding entry in multipath.conf is:
vendor "DGC"
product "*"
I suspect from the output below that you want:
vendor "DELL"
product "DELL,MD Virtual Disk"
But check in sysfs.
> multipaths { mulitpath { device { vendor DELL product MD3000i } } }
>
This block does not define anything.
> After changing the multipath.conf I did:
>
> multipath -F service multipathd restart
>
> Now, if I've do:
>
> # multipath -ll mpathe (36002219000918b4c00005b6c497e6632) dm-4
> DELL,MD Virtual Disk [size=5.5T][features=0][hwhandler=0] \_
> round-robin 0 [prio=1][active] \_ 9:0:0:1 sdi 8:128
> [active][ready]
Your settings are being ignored, probably because of a vendor/product
mismatch.
Regards,
Bryn.
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
^ permalink raw reply [flat|nested] 15+ messages in thread* Re: Multipath setup and rdac questions
2009-02-05 17:37 ` Moger, Babu
@ 2009-02-05 17:44 ` Bryn M. Reeves
2009-02-05 17:51 ` Moger, Babu
2009-02-05 17:52 ` Moger, Babu
2009-02-05 19:13 ` Christian Røsnes
1 sibling, 2 replies; 15+ messages in thread
From: Bryn M. Reeves @ 2009-02-05 17:44 UTC (permalink / raw)
To: device-mapper development
Moger, Babu wrote:
> Like Bryn said, you cannot have both MPP and device mapper together. MPP will be the first one to load. So it will claim all the devices.
>
> I have modified your multipath.conf file. Please try this one below.
>
> devices {
> device {
> vendor "DELL"
> product "MD3000i"
Are these actually correct? The -ll output the OP posted seemed to
indicate his settings were being completely ignored (which usually
suggests a vendor/product mismatch).
It would be good to get all the correct vendor/product details for the
3000 models included upstream at some point so that users don't need
to add their own device blocks.
Regards,
Bryn.
^ permalink raw reply [flat|nested] 15+ messages in thread* RE: Multipath setup and rdac questions
2009-02-05 17:44 ` Bryn M. Reeves
@ 2009-02-05 17:51 ` Moger, Babu
2009-02-05 17:52 ` Moger, Babu
1 sibling, 0 replies; 15+ messages in thread
From: Moger, Babu @ 2009-02-05 17:51 UTC (permalink / raw)
To: bmr@redhat.com, device-mapper development
Please run "/proc/scsi/scsi" to get the correct vendor and product ids.
Thanks
Babu Moger
-----Original Message-----
From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com] On Behalf Of Bryn M. Reeves
Sent: Thursday, February 05, 2009 11:45 AM
To: device-mapper development
Subject: Re: [dm-devel] Multipath setup and rdac questions
Moger, Babu wrote:
> Like Bryn said, you cannot have both MPP and device mapper together. MPP will be the first one to load. So it will claim all the devices.
>
> I have modified your multipath.conf file. Please try this one below.
>
> devices {
> device {
> vendor "DELL"
> product "MD3000i"
Are these actually correct? The -ll output the OP posted seemed to
indicate his settings were being completely ignored (which usually
suggests a vendor/product mismatch).
It would be good to get all the correct vendor/product details for the
3000 models included upstream at some point so that users don't need
to add their own device blocks.
Regards,
Bryn.
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
^ permalink raw reply [flat|nested] 15+ messages in thread* RE: Multipath setup and rdac questions
2009-02-05 17:44 ` Bryn M. Reeves
2009-02-05 17:51 ` Moger, Babu
@ 2009-02-05 17:52 ` Moger, Babu
1 sibling, 0 replies; 15+ messages in thread
From: Moger, Babu @ 2009-02-05 17:52 UTC (permalink / raw)
To: bmr@redhat.com, device-mapper development
Please run "cat /proc/scsi/scsi"
Thanks
Babu Moger
-----Original Message-----
From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com] On Behalf Of Bryn M. Reeves
Sent: Thursday, February 05, 2009 11:45 AM
To: device-mapper development
Subject: Re: [dm-devel] Multipath setup and rdac questions
Moger, Babu wrote:
> Like Bryn said, you cannot have both MPP and device mapper together. MPP will be the first one to load. So it will claim all the devices.
>
> I have modified your multipath.conf file. Please try this one below.
>
> devices {
> device {
> vendor "DELL"
> product "MD3000i"
Are these actually correct? The -ll output the OP posted seemed to
indicate his settings were being completely ignored (which usually
suggests a vendor/product mismatch).
It would be good to get all the correct vendor/product details for the
3000 models included upstream at some point so that users don't need
to add their own device blocks.
Regards,
Bryn.
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: Multipath setup and rdac questions
2009-02-05 17:37 ` Moger, Babu
2009-02-05 17:44 ` Bryn M. Reeves
@ 2009-02-05 19:13 ` Christian Røsnes
2009-02-05 19:16 ` Bryn M. Reeves
1 sibling, 1 reply; 15+ messages in thread
From: Christian Røsnes @ 2009-02-05 19:13 UTC (permalink / raw)
To: device-mapper development
[-- Attachment #1.1: Type: text/plain, Size: 4471 bytes --]
On Thu, Feb 5, 2009 at 6:37 PM, Moger, Babu <Babu.Moger@lsi.com> wrote:
>
> Like Bryn said, you cannot have both MPP and device mapper together. MPP
> will be the first one to load. So it will claim all the devices.
>
> I have modified your multipath.conf file. Please try this one below.
>
> devices {
> device {
> vendor "DELL"
> product "MD3000i"
> product_blacklist "Universal Xport"
> features "1 queue_if_no_path"
> path_grouping_policy group_by_prio
> prio_callout "/sbin/mpath_prio_rdac /dev/%n"
> getuid_callout "/sbin/scsi_id -g -u -s
> /block/%n"
> hardware_handler "1 rdac"
> path_checker rdac
> prio "rdac"
> failback immediate
> }
> }
>
> Hi
Thank you for the information.
I changed my multipath.conf to the following:
cat /etc/multipath.conf
defaults {
udev_dir /dev
user_friendly_names yes
}
blacklist {
devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
devnode "^hd[a-z]"
devnode "^sda"
devnode "^sda[0-9]"
}
devices {
device {
vendor "DELL"
product "MD Virtual Disk"
product_blacklist "Universal Xport"
features "1 queue_if_no_path"
path_grouping_policy group_by_prio
prio_callout "/sbin/mpath_prio_rdac /dev/%n"
getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
hardware_handler "1 rdac"
path_checker rdac
prio "rdac"
failback immediate
}
}
then did:
# multipath -F
# service multipathd restart
Now I get:
# multipath -ll
mpathe (36002219000918b4c00005b6c497e6632) dm-4 DELL,MD Virtual Disk
[size=5.5T][features=1 queue_if_no_path][hwhandler=1 rdac]
\_ round-robin 0 [prio=6][active]
\_ 9:0:0:1 sdi 8:128 [active][ready]
mpathd (36002219000918b3300002e6e497e6315) dm-3 DELL,MD Virtual Disk
[size=5.5T][features=1 queue_if_no_path][hwhandler=1 rdac]
\_ round-robin 0 [prio=6][active]
\_ 9:0:0:2 sdj 8:144 [active][ready]
mpathc (36002219000918b4c00005b6f497e6695) dm-2 DELL,MD Virtual Disk
[size=5.5T][features=1 queue_if_no_path][hwhandler=1 rdac]
\_ round-robin 0 [prio=6][active]
\_ 9:0:0:3 sdk 8:160 [active][ready]
mpathb (36002219000918b3300002e71497e6378) dm-1 DELL,MD Virtual Disk
[size=5.5T][features=1 queue_if_no_path][hwhandler=1 rdac]
\_ round-robin 0 [prio=6][active]
\_ 9:0:0:4 sdl 8:176 [active][ready]
mpatha (36002219000918b4c00005b72497e66f3) dm-0 DELL,MD Virtual Disk
[size=5.5T][features=1 queue_if_no_path][hwhandler=1 rdac]
\_ round-robin 0 [prio=6][active]
\_ 9:0:0:5 sdm 8:192 [active][ready]
mpathl (36002219000918b3300002e6b497e62a6) dm-11 DELL,MD Virtual Disk
[size=5.5T][features=1 queue_if_no_path][hwhandler=1 rdac]
\_ round-robin 0 [prio=6][active]
\_ 9:0:0:0 sdb 8:16 [active][ready]
mpathk (36002219000922cdf000004a4497e53f5) dm-10 DELL,MD Virtual Disk
[size=5.5T][features=1 queue_if_no_path][hwhandler=1 rdac]
\_ round-robin 0 [prio=6][active]
\_ 9:0:1:10 sdc 8:32 [active][ready]
mpathj (36002219000918b2e000004b2497e581c) dm-9 DELL,MD Virtual Disk
[size=5.5T][features=1 queue_if_no_path][hwhandler=1 rdac]
\_ round-robin 0 [prio=6][active]
\_ 9:0:1:11 sdd 8:48 [active][ready]
mpathi (36002219000922cdf000004a7497e54dd) dm-8 DELL,MD Virtual Disk
[size=5.5T][features=1 queue_if_no_path][hwhandler=1 rdac]
\_ round-robin 0 [prio=6][active]
\_ 9:0:1:12 sde 8:64 [active][ready]
mpathh (36002219000918b2e000004b5497e587e) dm-7 DELL,MD Virtual Disk
[size=5.5T][features=1 queue_if_no_path][hwhandler=1 rdac]
\_ round-robin 0 [prio=6][active]
\_ 9:0:1:13 sdf 8:80 [active][ready]
mpathg (36002219000922cdf000004aa497e5532) dm-6 DELL,MD Virtual Disk
[size=5.5T][features=1 queue_if_no_path][hwhandler=1 rdac]
\_ round-robin 0 [prio=6][active]
\_ 9:0:1:14 sdg 8:96 [active][ready]
mpathf (36002219000918b2e000004b8497e58dc) dm-5 DELL,MD Virtual Disk
[size=5.5T][features=1 queue_if_no_path][hwhandler=1 rdac]
\_ round-robin 0 [prio=6][active]
\_ 9:0:1:15 sdh 8:112 [active][ready]
Thank you
Christian
[-- Attachment #1.2: Type: text/html, Size: 8112 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
^ permalink raw reply [flat|nested] 15+ messages in thread* Re: Multipath setup and rdac questions
2009-02-05 19:13 ` Christian Røsnes
@ 2009-02-05 19:16 ` Bryn M. Reeves
2009-02-05 19:23 ` Christian Røsnes
0 siblings, 1 reply; 15+ messages in thread
From: Bryn M. Reeves @ 2009-02-05 19:16 UTC (permalink / raw)
To: device-mapper development
Christian Røsnes wrote:
> # multipath -ll
> mpathe (36002219000918b4c00005b6c497e6632) dm-4 DELL,MD Virtual Disk
> [size=5.5T][features=1 queue_if_no_path][hwhandler=1 rdac]
> \_ round-robin 0 [prio=6][active]
> \_ 9:0:0:1 sdi 8:128 [active][ready]
That looks better! Seems like device-mapper multipath is configuring
these OK now. You might want to just check that mpp is fully disabled
if you're going with device-mapper (and also test some cable-pulls to
make sure the RDAC failover happens properly) but this is certainly
picking up your hw handler configuration now.
Regards,
Bryn.
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: Multipath setup and rdac questions
2009-02-05 19:16 ` Bryn M. Reeves
@ 2009-02-05 19:23 ` Christian Røsnes
0 siblings, 0 replies; 15+ messages in thread
From: Christian Røsnes @ 2009-02-05 19:23 UTC (permalink / raw)
To: bmr, device-mapper development
[-- Attachment #1.1: Type: text/plain, Size: 870 bytes --]
On Thu, Feb 5, 2009 at 8:16 PM, Bryn M. Reeves <bmr@redhat.com> wrote:
> Christian Røsnes wrote:
>
>> # multipath -ll
>> mpathe (36002219000918b4c00005b6c497e6632) dm-4 DELL,MD Virtual Disk
>> [size=5.5T][features=1 queue_if_no_path][hwhandler=1 rdac]
>> \_ round-robin 0 [prio=6][active]
>> \_ 9:0:0:1 sdi 8:128 [active][ready]
>>
>
> That looks better! Seems like device-mapper multipath is configuring these
> OK now. You might want to just check that mpp is fully disabled if you're
> going with device-mapper (and also test some cable-pulls to make sure the
> RDAC failover happens properly) but this is certainly picking up your hw
> handler configuration now.
>
>
Ok. I'll look into disabling mpp, and test the device-mapper failover by
pulling cables and manually switching controller modules during
disk access.
Thank you.
Christian
[-- Attachment #1.2: Type: text/html, Size: 1374 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: Multipath setup and rdac questions
2009-02-05 15:07 ` Bryn M. Reeves
2009-02-05 17:37 ` Moger, Babu
@ 2009-02-05 18:48 ` Christian Røsnes
2009-02-05 19:11 ` Bryn M. Reeves
2009-02-05 19:29 ` Chandra Seetharaman
2009-02-05 18:56 ` Christian Røsnes
2 siblings, 2 replies; 15+ messages in thread
From: Christian Røsnes @ 2009-02-05 18:48 UTC (permalink / raw)
To: bmr, device-mapper development
[-- Attachment #1.1: Type: text/plain, Size: 2230 bytes --]
On Thu, Feb 5, 2009 at 4:07 PM, Bryn M. Reeves <bmr@redhat.com> wrote:
> Christian Røsnes wrote:
>
>>
> I also see these messages in /var/log/messages when I change the
>> module controller ownership:
>>
>> 494 [RAIDarray.mpp]MD3000i_A:0:1:0 Cmnd-failed try alt ctrl 1.
>> vcmnd SN 351494 pdev H2:C0:T0:L0 0x05/0x94/0x01 0x08000002
>> mpp_status:1
>>
>
> Don't know where this is coming form. Do you have IBM's MPP
> multipathing driver installed? If you are using device-mapper
> multipath and multipath tools (the rest of your mail suggests this is
> your intention) you should not load the MPP modules.
>
> Hi
Thank you for the information.
I think the MPP driver came from the
linuxrdac-09.03.0C06.0030-1dkms rpm package
installed from the Dell MD3000i Resource CD,
because the top of the Makefile in /usr/src/linuxrdac-09.03.0C06.0030 reads:
#**********************************************************************
# Makefile for Linux RDAC (MPP) Driver
#
# This is a modified version of the linuxrdac Makefile provided by LSI
# (renamed to Makefile_orig).
# It is dkms compatable, and provides:
# genuniqueid, mppUtil, install, uninstall
# The mppUpper and mppVhba targets are provided by dkms through obj-m
#
#######################################################################
It was maybe installed when I choose this option 3 from the installer on
that CD:
-------------------------------------------------------------------------------------------------------------
################################################################
Dell PowerVault MD3000i Resource CD
################################################################
1. View MD3000i Readme
2. Install MD3000i Storage Manager
3. Install Multi-pathing Driver
4. MD3000i Configuration Utility
5. Dell Support
6. View End User License Agreement
Enter the number to select a component from the above list.
Enter q to quit.
Enter: 3
-------------------------------------------------------------------------------------------------------------
Is mpp another type of rdac driver than the one in question here ?
Thank you
Christian
[-- Attachment #1.2: Type: text/html, Size: 3328 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
^ permalink raw reply [flat|nested] 15+ messages in thread* Re: Multipath setup and rdac questions
2009-02-05 18:48 ` Christian Røsnes
@ 2009-02-05 19:11 ` Bryn M. Reeves
2009-02-05 19:29 ` Chandra Seetharaman
1 sibling, 0 replies; 15+ messages in thread
From: Bryn M. Reeves @ 2009-02-05 19:11 UTC (permalink / raw)
To: device-mapper development
Christian Røsnes wrote:
> Is mpp another type of rdac driver than the one in question here ?
I have no real experience with MPP so there are probably others who
can give more details but MPP is an entirely separate 3rd-party
multipath driver framework, a bit like EMC's PowerPath or other
vendor's multipathing solutions. Afaik, it supports several types of
device including RDAC.
Part of your problem appears to be that you are trying to use /both/
mpp and device-mapper multipath on the same system at the same time.
Since they both try to do the same job this is guaranteed to lead to
problems - you need to chose one or the other & get it correctly
configured for your hardware.
Regards,
Bryn.
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: Multipath setup and rdac questions
2009-02-05 18:48 ` Christian Røsnes
2009-02-05 19:11 ` Bryn M. Reeves
@ 2009-02-05 19:29 ` Chandra Seetharaman
2009-02-05 19:30 ` Christian Røsnes
1 sibling, 1 reply; 15+ messages in thread
From: Chandra Seetharaman @ 2009-02-05 19:29 UTC (permalink / raw)
To: device-mapper development; +Cc: bmr
On Thu, 2009-02-05 at 19:48 +0100, Christian Røsnes wrote:
>
> Is mpp another type of rdac driver than the one in question here ?
Yes, MPP is a standalone out-of-tree driver provided by LSI to support
the rdac devices.
Now that rdac support is available in mainline and distro, you do not
need to use them anymore.
MPP driver sits below the SCSI layer and manages all the
failover/failback. It takes the MD3000i devices and provides the
"virtual disk" to the SCSI layer. That is the reason why you do not see
the MD3000i from user space.
Once you remove the mpp driver and use the multipathy.conf provided by
Babu, you should see the behavior you expect.
>
>
>
> Thank you
> Christian
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: Multipath setup and rdac questions
2009-02-05 19:29 ` Chandra Seetharaman
@ 2009-02-05 19:30 ` Christian Røsnes
0 siblings, 0 replies; 15+ messages in thread
From: Christian Røsnes @ 2009-02-05 19:30 UTC (permalink / raw)
To: sekharan, device-mapper development
[-- Attachment #1.1: Type: text/plain, Size: 861 bytes --]
On Thu, Feb 5, 2009 at 8:29 PM, Chandra Seetharaman <sekharan@us.ibm.com>wrote:
>
> On Thu, 2009-02-05 at 19:48 +0100, Christian Røsnes wrote:
>
> >
> > Is mpp another type of rdac driver than the one in question here ?
>
> Yes, MPP is a standalone out-of-tree driver provided by LSI to support
> the rdac devices.
>
> Now that rdac support is available in mainline and distro, you do not
> need to use them anymore.
>
> MPP driver sits below the SCSI layer and manages all the
> failover/failback. It takes the MD3000i devices and provides the
> "virtual disk" to the SCSI layer. That is the reason why you do not see
> the MD3000i from user space.
>
> Once you remove the mpp driver and use the multipathy.conf provided by
> Babu, you should see the behavior you expect.
>
>
Ok. I will remove the mpp driver.
Thank you
Christian
[-- Attachment #1.2: Type: text/html, Size: 1218 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: Multipath setup and rdac questions
2009-02-05 15:07 ` Bryn M. Reeves
2009-02-05 17:37 ` Moger, Babu
2009-02-05 18:48 ` Christian Røsnes
@ 2009-02-05 18:56 ` Christian Røsnes
2009-02-05 19:13 ` Bryn M. Reeves
2 siblings, 1 reply; 15+ messages in thread
From: Christian Røsnes @ 2009-02-05 18:56 UTC (permalink / raw)
To: bmr, device-mapper development
[-- Attachment #1.1: Type: text/plain, Size: 775 bytes --]
On Thu, Feb 5, 2009 at 4:07 PM, Bryn M. Reeves <bmr@redhat.com> wrote:
> Christian Røsnes wrote:
>
> u should check what the MD3000i reports in sysfs. E.g. for an EMC
> clariion device I see:
>
> # cat /sys/block/sdj/device/vendor
> DGC
> # cat /sys/block/sdj/device/model
> RAID 5
>
> And the corresponding entry in multipath.conf is:
>
> vendor "DGC"
> product "*"
>
> I suspect from the output below that you want:
>
> vendor "DELL"
> product "DELL,MD Virtual Disk"
>
>
Here's what I see for the MD3000i:
# cat /sys/block/sdb/device/vendor
DELL
# cat /sys/block/sdb/device/model
MD Virtual Disk
Thank you
Christian
[-- Attachment #1.2: Type: text/html, Size: 1496 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: Multipath setup and rdac questions
2009-02-05 18:56 ` Christian Røsnes
@ 2009-02-05 19:13 ` Bryn M. Reeves
0 siblings, 0 replies; 15+ messages in thread
From: Bryn M. Reeves @ 2009-02-05 19:13 UTC (permalink / raw)
To: Christian Røsnes; +Cc: device-mapper development
Christian Røsnes wrote:
>>
>> vendor "DGC"
>> product "*"
>>
>> I suspect from the output below that you want:
>>
>> vendor "DELL"
>> product "DELL,MD Virtual Disk"
>>
>>
> Here's what I see for the MD3000i:
>
> # cat /sys/block/sdb/device/vendor
> DELL
> # cat /sys/block/sdb/device/model
> MD Virtual Disk
>
> Thank you
> Christian
>
That's what I thought based on the output you posted earlier. You need
to put this in multipath.conf instead of the values you currently have
("DELL"/"MD3000i" which are not correct for this hardware) but you
also need to resolve the issue of whether you want to use
device-mapper or MPP multipathing - the /etc/multipath.conf file is
only used by the device-mapper multipath tools.
Regards,
Bryn.
^ permalink raw reply [flat|nested] 15+ messages in thread
end of thread, other threads:[~2009-02-05 19:30 UTC | newest]
Thread overview: 15+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-02-05 13:58 Multipath setup and rdac questions Christian Røsnes
2009-02-05 15:07 ` Bryn M. Reeves
2009-02-05 17:37 ` Moger, Babu
2009-02-05 17:44 ` Bryn M. Reeves
2009-02-05 17:51 ` Moger, Babu
2009-02-05 17:52 ` Moger, Babu
2009-02-05 19:13 ` Christian Røsnes
2009-02-05 19:16 ` Bryn M. Reeves
2009-02-05 19:23 ` Christian Røsnes
2009-02-05 18:48 ` Christian Røsnes
2009-02-05 19:11 ` Bryn M. Reeves
2009-02-05 19:29 ` Chandra Seetharaman
2009-02-05 19:30 ` Christian Røsnes
2009-02-05 18:56 ` Christian Røsnes
2009-02-05 19:13 ` Bryn M. Reeves
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.