From: Mike Christie <michaelc@cs.wisc.edu>
To: axboe@suse.de, dm-devel@redhat.com, linux-scsi@vger.kernel.org
Subject: [ANNOUNCE] block layer (request based) multipath v1
Date: Wed, 19 Oct 2005 01:20:44 -0500 [thread overview]
Message-ID: <4355E5BC.60701@cs.wisc.edu> (raw)
Version 1 and maybe the only version :)
I have pretty much completely convert dm-multipath to blk_mpath. I
converted the hw handlers (including the out of tree hp-sw and
engenio-rdac ones) and implemented the emc sense code for Read/Write
errors. The next task would be to completely convert the open source
Engenio driver which I had started doing for dm-multipath and the eroro
code patches but ended up having problems with the sense decoding.
The large patch is here
http://www.cs.wisc.edu/~michaelc/block/blk_mpath/blk_mpath3.patch
I think the only items I have left to convert are some of the dm ioctls,
but that is trivial and the defaults are ok for usage. For example I
have not implemted a sysfs attr to read/write queue_if_no_path and a
timeout attr so we do not have to wait forever on it.
Comments???? Should I work with Christophe to convert the userspace tools?
Changed since last post:
- Fixed partial completion code to support existing scenarios
(for example SCSI MEDIUM ERRORS where the head is completed ok but the
end could end up failed or ok)
- converted dm-hw_handler code
- Completely converted dm-emc.c including adding RW error sense code
- Added hp-sw and engenio rdac code for failover. I will send sense code
support when finished gettitng access from OSDL and can test that code,
but it should basically work but just not so effeciently and when doing
snapshots or backups or firmware upgrades or other features. Maybe
Engenio could just implement this now since all the pieces are there,
except maybe controller representation, or at least give me some docs so
I do not have to guess about some of the code in the GPL driver :)
- Added a path state sysfs attr for onlining paths. Userspace can online
a path and do failback now.
reply other threads:[~2005-10-19 6:20 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=4355E5BC.60701@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=axboe@suse.de \
--cc=dm-devel@redhat.com \
--cc=linux-scsi@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).