Hey Joel, sorry for not replying sooner, but I've been up to my eyeballs in
work.
iscsi targets setup via "ZFS set shareiscsi=on" do not support storing any
of the iscsi settings. This is a known issue and (IMNSHO) makes shareiscsi
next to useless (there has been some discussion on the topic in the past,
but there is no plan to change this). What you need to do is create your
zvol, then create a iscsi-target using "iscsitadm create target
-b /dev/zvol/rdsk/pool/mylun <alias for target>" I have been using
incremental numbers for the alias.
This method will also allow you to create other LUNs by adding the -u 1 to
the iscsitadm command.
Andrew Hettinger
http://Prominic.NET || [EMAIL PROTECTED]
Tel: 866.339.3169 (toll free) -or- +1.217.356.2888 x.110 (int'l)
Fax: 866.372.3356 (toll free) -or- +1.217.356.3356 (int'l)
Mobile direct: 1.217.621.2540
CompTIA A+, CompTIA Network+, MCP
Joel Weinberger <[EMAIL PROTECTED]> wrote on 11/29/2007 03:31:46 PM:
> My previous question seems to have answered itself, and regular file
> backed iscsi targets work just fine with SMF as far as I can tell.
> However, I am still having the same problem with ZFS LUNs. They simply
> don't seem to appear as properties in SMF for iscsitgt. I also cannot
> create the equivalent properties in SMF because the LUN target names are
> the dataset names, "pool/mylun", for example, and because of the slash
> in the target name, the iscsitgt convention of "target_name" for the
> property group fails since there cannot be a slash in a property group
> name. Any suggestions for how to deal with ZFS LUNs and the iscsitgt
> service? Thanks.
>
> --
> Joel Weinberger, Fishworks
>
> _______________________________________________
> storage-discuss mailing list
> [email protected]
> http://mail.opensolaris.org/mailman/listinfo/storage-discuss
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
