Hello, I'd like to add my observations to the discussion here. I'm having the same issues with globalSAN as cmack. I'm running globalSAN 3.3.0.35 on a MacBook Pro OS X 10.5.2.
My OpenSolaris Target is: # uname -a SunOS athena 5.11 snv_79a i86pc i386 i86pc # isainfo -kv 64-bit amd64 kernel modules I created an iSCSI target through a zfs create command: # zfs create -V 300G -o shareiscsi=on tank/TimeMachine When I point globalSAN at the iSCSI machine (through the portal tab) it doesn't find the target device. GlobalSAN does automatially find the target device if I point it at a FreeBSD iSCSI system. So, I had to enter the target manually. I press the "Log On..." button and globalSAN reports a connection; however, iscsitadm does not report the connection. Drive utility on the Mac doesn't show the device connected. I believe the above paragraph is pretty much in lock step with cmack's issues. However, if you leave the system sit for about 30-40 minutes, the device does appear in the Disk Utility. Any attempts to manipulate the volume (including ejecting) results in timeouts and lockups. I don't know if that helps the debugging process, or if it just adds flotsam to the discussion. HTH! Regards, Mark This message posted from opensolaris.org _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
