From: Jakov Sosic <jakov.sosic@srce.hr>
To: dm-devel@redhat.com
Subject: Re: Sun StorageTek 2530 and dm?
Date: Mon, 24 Aug 2009 23:53:47 +0200 [thread overview]
Message-ID: <20090824235347.4b8cbd8a@pc-jsosic.srce.hr> (raw)
In-Reply-To: <1251150116.24406.37.camel@chandra-ubuntu>
On Mon, 24 Aug 2009 14:41:56 -0700
Chandra Seetharaman <sekharan@us.ibm.com> wrote:
> These messages are seen because there is no support for this device
> in-built in the scsi_dh_rdac module.
>
> These will disappear when youadded the device support to scsi_dh_rdac
> module and include the module in your initrd image.
Now if I understand correctly - because my device is not
supported by scsi_dh_rdac - RDAC is not functional at all? Because
later in the dmesg, it shows
sd 1:0:1:0: rdac: LUN 0 (owned)
sd 1:0:0:0: rdac: LUN 0 (unowned)
which suggests that RDAC is working after all?
Here is my current multipath.conf (Sbeaf_11 and Sbeaf_21 are iSCSI
targets that work flawlessly):
defaults {
user_friendly_names yes
}
defaults {
udev_dir /dev
polling_interval 10
selector "round-robin 0"
path_grouping_policy multibus
getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
prio_callout /bin/true
path_checker readsector0
rr_min_io 100
max_fds 8192
rr_weight priorities
failback immediate
no_path_retry fail
user_friendly_names yes
}
blacklist {
devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
devnode "^hd[a-z]"
}
multipaths {
multipath {
wwid S_beaf11
alias controller0
path_grouping_policy failover
path_checker readsector0
path_selector "round-robin 0"
failback immediate
no_path_retry queue
}
multipath {
wwid S_beaf21
alias controller1
path_grouping_policy failover
path_checker readsector0
path_selector "round-robin 0"
failback immediate
no_path_retry queue
}
multipath {
wwid
3600a0b80002fcd18000014544a9166fb
alias sas-xen
}
multipath {
wwid
3600a0b80003abc5c00000b654a916617
alias sas-mysql
}
multipath {
wwid
3600a0b80002fcd18000014514a9165b4
alias qd
}
}
devices {
device {
vendor "SUN"
product "LCSM100_S"
getuid_callout "/sbin/scsi_id -g -u
-s /block/%n"
prio_callout "/sbin/mpath_prio_tpc /dev/%n"
hardware_handler "1 rdac"
path_grouping_policy group_by_prio
path_checker rdac
failback immediate
rr_weight uniform
no_path_retry queue
rr_min_io 1000
}
}
And here is the multipath -ll:
# multipath -ll
qd (3600a0b80002fcd18000014514a9165b4) dm-0 SUN,LCSM100_S
[size=100M][features=1 queue_if_no_path][hwhandler=1 rdac][rw]
\_ round-robin 0 [prio=3][active]
\_ 1:0:1:0 sde 8:64 [active][ready]
\_ round-robin 0 [prio=0][enabled]
\_ 1:0:0:0 sdb 8:16 [active][ghost]
controller1 (S_beaf21) dm-4 IET,VIRTUAL-DISK
[size=3.4T][features=1 queue_if_no_path][hwhandler=0][rw]
\_ round-robin 0 [prio=0][active]
\_ 8:0:0:1 sdk 8:160 [active][ready]
\_ round-robin 0 [prio=0][enabled]
\_ 9:0:0:1 sdj 8:144 [active][ready]
controller0 (S_beaf11) dm-3 IET,VIRTUAL-DISK
[size=3.4T][features=1 queue_if_no_path][hwhandler=0][rw]
\_ round-robin 0 [prio=0][active]
\_ 10:0:0:1 sdh 8:112 [active][ready]
\_ round-robin 0 [prio=0][enabled]
\_ 11:0:0:1 sdi 8:128 [active][ready]
sas-mysql (3600a0b80003abc5c00000b654a916617) dm-1 SUN,LCSM100_S
[size=115G][features=1 queue_if_no_path][hwhandler=1 rdac][rw]
\_ round-robin 0 [prio=3][active]
\_ 1:0:1:1 sdf 8:80 [active][ready]
\_ round-robin 0 [prio=0][enabled]
\_ 1:0:0:1 sdc 8:32 [active][ghost]
sas-xen (3600a0b80002fcd18000014544a9166fb) dm-2 SUN,LCSM100_S
[size=21G][features=1 queue_if_no_path][hwhandler=1 rdac][rw]
\_ round-robin 0 [prio=3][active]
\_ 1:0:0:2 sdd 8:48 [active][ready]
\_ round-robin 0 [prio=0][enabled]
\_ 1:0:1:2 sdg 8:96 [active][ghost]
--
| Jakov Sosic | ICQ: 28410271 | PGP: 0x965CAE2D |
=================================================================
| start fighting cancer -> http://www.worldcommunitygrid.org/ |
next prev parent reply other threads:[~2009-08-24 21:53 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-23 19:05 Sun StorageTek 2530 and dm? Jakov Sosic
2009-08-23 19:34 ` Jakov Sosic
2009-08-24 15:41 ` Charlie Brady
2009-08-24 15:48 ` Jakov Sosic
2009-08-24 16:00 ` Jakov Sosic
2009-08-24 18:38 ` Chandra Seetharaman
2009-08-24 18:55 ` Jakov Sosic
2009-08-24 20:24 ` Chandra Seetharaman
2009-08-24 20:37 ` Jakov Sosic
2009-08-24 20:44 ` Chandra Seetharaman
2009-08-24 20:53 ` Jakov Sosic
2009-08-24 21:06 ` Chandra Seetharaman
2009-08-24 21:37 ` Jakov Sosic
2009-08-24 21:54 ` Chandra Seetharaman
2009-08-24 22:58 ` Charlie Brady
2009-08-24 23:09 ` Jakov Sosic
2009-08-24 23:18 ` Chandra Seetharaman
2009-08-24 23:22 ` Jakov Sosic
2009-08-24 23:11 ` Chandra Seetharaman
2009-08-24 23:11 ` Jakov Sosic
2009-08-24 18:29 ` Jakov Sosic
2009-08-24 18:48 ` Chandra Seetharaman
2009-08-24 18:59 ` Jakov Sosic
2009-08-24 20:24 ` Chandra Seetharaman
2009-08-24 20:36 ` Jakov Sosic
2009-08-24 20:57 ` Chandra Seetharaman
2009-08-24 21:14 ` Jakov Sosic
2009-08-24 21:41 ` Chandra Seetharaman
2009-08-24 21:53 ` Jakov Sosic [this message]
2009-08-24 23:07 ` Chandra Seetharaman
2009-08-24 23:13 ` Jakov Sosic
2009-08-25 0:06 ` Jakov Sosic
2009-08-25 0:18 ` Chandra Seetharaman
2009-08-25 3:36 ` Charlie Brady
2009-08-25 18:07 ` Chandra Seetharaman
2009-08-25 19:21 ` Charlie Brady
2009-08-25 19:55 ` Chandra Seetharaman
2009-08-25 20:51 ` Charlie Brady
2009-08-25 21:09 ` Jakov Sosic
2009-08-26 21:57 ` Charlie Brady
2009-08-26 22:31 ` Chandra Seetharaman
2009-08-26 23:01 ` Charlie Brady
2009-08-27 8:30 ` Jakov Sosic
2009-08-27 16:02 ` Charlie Brady
2009-08-27 19:11 ` Chandra Seetharaman
2009-08-24 21:19 ` Jakov Sosic
2009-08-24 21:43 ` Chandra Seetharaman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090824235347.4b8cbd8a@pc-jsosic.srce.hr \
--to=jakov.sosic@srce.hr \
--cc=dm-devel@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.