Hi, I am working with a customer who has an iSCSI SAN and who over the weekend upgraded a system from Solaris 8 to Solaris 10 update 2 and added an additional T2000 with S10u2. Previously the customer was using either QLOGIC iSCSI HBAs or Cisco's iSCSI software initiator (both of which had varoius quirks and the iSCSI SAN vendor urged them to move to S10's builtin initiator). One problem we ran into is that if we have the iSCSI backed filesystems set to mount at boot via vfstab, the filesystem/local service faults (saying it can't mount the iSCSI filesystems). If I go over to the console a minute later, I can clear the service and the mounts will come online fine, so it seems like there is an initial timeout issue and there should perhaps be an additional dependency or a change to the fs-local method.
Has anyone seen a similiar problem or know of a good workaround? There is an "iscsi_initiator" service, but by default it is disabled, and doesn't seem to have any dependencies related to filesystem/local. It starts the iscsid daemon and I didn't see a manpage that talked about what it actually did. This message posted from opensolaris.org
