Thomas Nau wrote:
Dear all.
I've setup the following scenario:
Galaxy 4200 running OpenSolaris build 59 as iSCSI target; remaining
diskspace of the two internal drives with a total of 90GB is used as
zpool for the two 32GB volumes "exported" via iSCSI
The initiator is an up to date Solaris 10 11/06 x86 box using the above
mentioned volumes as disks for a local zpool.
Like this?
disk--zpool--zvol--iscsitarget--network--iscsiclient--zpool--filesystem--app
> 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 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?
-- richard
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
