From: Mike Anderson <andmike@us.ibm.com>
To: dm-devel@redhat.com
Cc: axboe@suse.com
Subject: Question on dm-mp sense handling
Date: Wed, 23 Feb 2005 18:07:49 -0800 [thread overview]
Message-ID: <20050224020749.GA669@us.ibm.com> (raw)
Is someone still working on the sense buffer handling code for bios
to be used by dm-mp?
The ifdef'd out code in dm-emc.c and dm_scsi_err_handler appears to only
allow the interpretation of sense data if available and does not provide
any detail on non-sense based failures (DRIVER_TIMEOUT vs DID_* status).
An old patch that Mike Christie submitted was a start at mapping errors to
BLK error flags but did not receive much feedback. Is there some reason to
not decode down at the lower levels with a possible interface for vendor
specific mapping?
Old post can be found here.
http://marc.theaimsgroup.com/?l=linux-kernel&m=107961883914541&w=2
The reason I am asking the question is I am looking into issues of a
single device mapper hardware handler supporting block devices exported by
a DASD driver or through the SCSI subsystem.
-andmike
--
Michael Anderson
andmike@us.ibm.com
next reply other threads:[~2005-02-24 2:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 2:07 Mike Anderson [this message]
2005-04-10 19:11 ` Question on dm-mp sense handling Lars Marowsky-Bree
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=20050224020749.GA669@us.ibm.com \
--to=andmike@us.ibm.com \
--cc=axboe@suse.com \
--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