Here's a list of everyone who has responded so far to the request
for feedback to the storage_sig.  This was in response to an action
item from the June 23 storage sig phone conference call.

Responses From:
	Mike Christie		<mikenc@us.ibm.com>
	Lars Marowsky-Bree	<lmb@suse.de>
	Stefan Bader		<Stefan.Bader@de.ibm.com>
	Mike Anderson		<andmike@us.ibm.com>
	Badari Pulavarty	<pbadari@us.ibm.com>
	Timothy Witham		<wookie@osdl.org>
	Robert Wipfel		<RAWIPFEL@novell.com>
	
The files in this directory are attemtps to aggregate the email responses.
The files are:
	1. dm-todo-list
		A TODO list for DM, SCSI, and Block layer changes to
		produce multipath for 2.6.
		(Mike Christie, Stefan Bader, Timothy Witham, Mike Anderson)

	2. high-level-requirements
		High level requirements for multipath
		(Badari Pulavarty, Mike Christie)

	3. Suse
		Suse multipath in SLES9 is based on Device-Mapper
					(Lars Marowsky-Bree)

	4. iscsi
		iSCSI issues, mostly in resposne to Badari's mail
		in item 2 above.
		(Mike Christie, Robert Wipfel)

I've attempted to aggregate each of these sections, and put them
on my web site.  You can find them at:

	http://www.developer.osdl.org/dmo/storage-sig-feedback/

I'm still hoping to get some feedback from others on the list.
But perhaps that'll take more time.

One question I'm hoping to start addressing, is what can OSDL do
to help in the progress of multipath support in Linux.  What
equipment could we provide, etc.

One of the comments from Badari regarding fault insertion has
grabbed my interest.  We have some ideas on how to do some types
of fault insertion.  We have an idea on how to be able to intiate
hard disk failures, or to provide access to FC switches to fail
paths.

Does anyone have other ideas for approaches, or equipement that
would be helpful?


Thanks,
Dave Olien