From: Mike Christie <michaelc@cs.wisc.edu>
To: device-mapper development <dm-devel@redhat.com>
Subject: LSI/Engenio support
Date: Sat, 08 Oct 2005 00:15:23 -0500 [thread overview]
Message-ID: <434755EB.4000300@cs.wisc.edu> (raw)
Well, not really but the beginning becuase people keep asking for it. I
am working on sending the sense info up to the block layer and on how to
share scsi_decide_disposistion processing between dm and scsi for the
failover command processing. I do not really know EMC or HP HW, but do
know the LSI stuff a little bit since I worked on dm when I was at IBM.
I put a basic hw handler here
http://www.cs.wisc.edu/~michaelc/block/dm/dm-hw-handler/v4/
(you should apply all the patches and select engenio support)
There are also some fixes to the other functions in that patchset. I
have not gotton a good chance to test the hw handler against real HW,
instead I have been faking it with scsi_debug.
If some of the people with the LSI/Engenio/FASTt/DS4000 boxes that have
been requesting manual failover support have a chance, could you just
try this out real quick. I just want to make sure I have the failover
command correct, so just run dd and pull a cable and make sure IO goes
to the other paths. Nothing fancy.
Oh yeah check your log, you should see something like this:
Oct 7 23:59:42 max kernel: device-mapper: rdac: queueing MODE_PAGE
command on 8:32
Oct 7 23:59:42 max kernel: device-mapper: dm_scsi_end_rq: errors 134217730
Oct 7 23:59:42 max kernel:
Oct 7 23:59:42 max kernel: device-mapper: rdac: rdac_rq_error 0x8000002
Oct 7 23:59:42 max kernel: dm-engenio-rdac: Current: sense key: Illegal
RequestOct 7 23:59:42 max kernel: Additional sense: Invalid command
operation code
Your output will be different since the above is just from using
scsi_debug (send me your output).
The next step will be to handle the more fun cases where we need the
sense in the dm layer. Then we can do the preffered path stuff and all
those other features and possibly integrate AVT support if needed.
Thanks
reply other threads:[~2005-10-08 5:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=434755EB.4000300@cs.wisc.edu \
--to=michaelc@cs.wisc.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 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.