Messages in this thread | ![/](/images/icornerl.gif) | | Date | Wed, 26 Mar 2003 18:31:31 +1100 | From | Lincoln Dale <> | Subject | Re: [PATCH] ENBD for 2.5.64 |
| |
At 11:55 PM 25/03/2003 -0600, Matt Mackall wrote: > > Yeah, iSCSI handles all that and more. It's a behemoth of a > > specification. (whether a particular implementation implements all that > > stuff correctly is another matter...) > >Indeed, there are iSCSI implementations that do multipath and >failover.
iSCSI is a transport. logically, any "multipathing" and "failover" belongs in a layer above it -- typically as a block-layer function -- and not as a transport-layer function.
multipathing belongs elsewhere -- whether it be in MD, LVM, EVMS, DevMapper -- or in a commercial implementation such as Veritas VxDMP, HDS HDLM, EMC PowerPath, ...
>Both iSCSI and ENBD currently have issues with pending writes during >network outages. The current I/O layer fails to report failed writes >to fsync and friends.
these are not "iSCSI" or "ENBD" issues. these are issues with VFS.
cheers,
lincoln.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| ![\](/images/icornerr.gif) |