On 3/19/07, Rafael Navaza <[EMAIL PROTECTED]> wrote:
The "Bad XML response" occurs when you try to "read" the configuration files (doing something like "iscsitam list target") while those are being writed by iscsitgtd. This happens (for example) when the deamon add/remove a client connection. In your case this is due to the Windog Initiator that can't stay connected to the Solaris Target. Well, I'm new with Solaris so I can't be totally sure of this^^
When I'm only using zfs shareiscsi I need to restart the target service or destroy the volume and recreate for the xml config file to be recreated. I'm not sure where zfs stores its iscsi information, but when I also use the manual (iscsitadm create target -b ...) method the config.xml for this seems to stay in place. Regardless I'm having issues with trying to connect to the iscsi target. Its broken some how. I tried a quick test from an openfiler vmware image I've got some PDU errors trying to start the initiator against the b55b Solaris target. I'm surprised it's such a pita, makes me wonder if zfs is really worth the pain of solaris vs linux. Nicholas
_______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
