Hi Maurice, I "got" the importance of the AVS group. I was really hoping there was a way AVS was talking to DMU or lower. I appreciate the pointer to the blog that shows how to support multiple volumes in a pool, that was slick.
The iSCSI bridge to the volumes was just a was a quick workaround to simplify AVS supporting ZFS raid configurations. (Plus I didn't know how to setup AVS for multiple volumes with raid pools). The mirroring was not intended for iSCSI, it was the only way I knew to replicate a ZFS volume, again I didn't see the blog page. Still, not a bad work around for quick and dirty. Plus, I can't see it consuming more resources than synchronously replicating 5 or more physical volumes or slices. I was seriously thinking of hacking the linux dev_mapper port to hook the pools and present them as scsi targets. I don't like the idea. If someone mis-configures a ZFS pool to use a mapped device, it will cause a recursion of internal SCSI traffic. Any opinion on the idea ? Again thanks for the pointer to the blog. -- This message posted from opensolaris.org _______________________________________________ opensolaris-help mailing list opensolaris-help@opensolaris.org
