Richard,
Like this?
disk--zpool--zvol--iscsitarget--network--iscsiclient--zpool--filesystem--app
exactly
I'm in a way still hoping that it's a iSCSI related Problem as detecting
dead hosts in a network can be a non trivial problem and it takes quite
some time for TCP to timeout and inform the upper layers. Just a
guess/hope here that FC-AL, ... do better in this case
Actually, this is why NFS was invented. Prior to NFS we had something like:
disk--raw--ndserver--network--ndclient--filesystem--app
The problem is that our NFS, Mail, DB and other servers use mirrrored
disks located in different building on campus. Currently we use FCAL
devices and recently switched from UFS to ZFS. The drawback with FCAL is
that you always need to have a second infrastructure (not the real
problem) but with different components. Having all ethernet would be much
easier.
The problem is that the failure modes are very different for networks and
presumably reliable local disk connections. Hence NFS has a lot of error
handling code and provides well understood error handling semantics. Maybe
what you really want is NFS?
We thought about using NFS as backend for as much as possible applications
but we need to have redundancy for the fileserver itself too
Thomas
-----------------------------------------------------------------
GPG fingerprint: B1 EE D2 39 2C 82 26 DA A5 4D E0 50 35 75 9E ED
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
