From: Charles Slivkoff <slivkoff@cmu.edu>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Dell MD3200 - sd: Current: sense key: Illegal Request ASC=0x94 ASCQ=0x1ASC=0x94 ASCQ=0x1
Date: Thu, 03 Mar 2011 15:59:01 -0500 [thread overview]
Message-ID: <4D700115.8000500@cmu.edu> (raw)
In-Reply-To: <D8C50530D6022F40A817A35C40CC06A7065777D7C3@DUBX7MCDUB01.EMEA.DELL.COM>
On 03/03/2011 11:47 AM, Menny_Hamburger@Dell.com wrote:
>
> I know this is usually a wild goose chase, but what about the
> controller firmware? I can see from the profile that the controller
> FW is 07.70.06.63, while the latest according to the Dell
> compatibility matrix is 07.75.14.60
I'll look into this next.
On 03/03/2011 01:30 PM, Yanqing_Liu@Dell.com wrote:
>
> It seems that you mapped your LUNs some time after host bootup. That
> causes pseudo LUN 0 to be created. If you lay down DM using Dell
> software package, please invoke "rescan_dm_devs" for
> re-configuration.
I have used "rescan_dm_devs" before. This did not eliminate the pseudo
LUN 0.
I did manage to get rid of them, though, by un-mapping and re-mapping
the array virtual disks as LUNs 0 & 1, instead of LUNs 1 & 2. The
current array profile is here: http://tinypaste.com/64eebb
lsscsi now looks good. See http://tinypaste.com/3580a
Unfortunately, this did not help with the "Illegal Request" messages.
> We may need your related kernel message for further analysis. As to
> why setting "failback" to manual doesn't work on MD3200, the problem
> may be in multipathing daemon, in combination with SAS tranpportation
> trearing down all devices immediately after path loss. We've filed a
> bugzilla for this.
The latest syslog is here: http://tinypaste.com/87516
> BTW, what is your LVM setting for these devices?
The LUNs are each assigned to their own SCSI controller. Both LUNs (PVs)
are members of a single VG. The LVs are striped across the PVs, thus
allowing both paths to be used. The "lvdisplay -m" output is here:
http://tinypaste.com/7c42a
next prev parent reply other threads:[~2011-03-03 20:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 19:52 Dell MD3200 - sd: Current: sense key: Illegal Request ASC=0x94 ASCQ=0x1ASC=0x94 ASCQ=0x1 Charles Slivkoff
2011-03-02 3:35 ` Moger, Babu
2011-03-02 18:52 ` Charles Slivkoff
2011-03-02 19:28 ` Moger, Babu
2011-03-02 22:55 ` Charles Slivkoff
2011-03-03 4:32 ` Moger, Babu
2011-03-03 16:14 ` Charles Slivkoff
2011-03-03 16:47 ` Menny_Hamburger
2011-03-03 20:59 ` Charles Slivkoff [this message]
2011-03-04 4:34 ` Moger, Babu
2011-03-04 17:34 ` Charles Slivkoff
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=4D700115.8000500@cmu.edu \
--to=slivkoff@cmu.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox