It seems as though I can set ACLs on an iSCSI target that I've exported via ZFS's shareiscsi property, but that that modification doesn't persist. That's a bug: either we shouldn't allow you to set the property or we should persist it properly.
Jim, is it safe to assume that you agree that this is a bug? Adam On Fri, Nov 30, 2007 at 06:09:35AM -0500, Jim Dunham wrote: > To follow up Rick's posting, the support in ZFS for "set > shareiscsi=on ....", brings the ease of ZFS filesystem management to > iSCSI Targets, similar to that of "set sharenfs=on ..." for NFS. > > With this ZFS functionality, also comes the capability for other > zvols created in the same ZFS directory structure to automatically be > created on demand. Also if a ZFS storage pool contains iSCSI Targets, > when zpool exported the iSCSI Targets will be torn down, when zpool > imported the iSCSI Targets will be recreated. > > Once a user of this ZFS functionality wants access to additional > features of iSCSI Target, they will need to stop using shareiscsi, > and directly configure their ZFS zvols using iscsitadm. Making this > change will not destroy the data contained on the ZVOL, but it will > change the iSCSI Target's identifier, requiring rediscovery by an > iSCSI initiator. > > Jim > > On Nov 29, 2007, at 7:54 PM, Rick McNeal wrote: > > > I haven't been following the complete thread here, but I can shed some > > light on what's happening with the ZFS luns. The target information > > for a ZFS iSCSI LU is stored with the ZFS zvol as a property. The > > iSCSI Target daemon has no knowledge of the the ZVOL until ZFS shares > > that volume through a private interface. It's possible to view the > > information using the zfs commands, but by default the data is not > > displayed. > > > > On Nov 29, 2007 2:31 PM, Joel Weinberger <[EMAIL PROTECTED]> > > wrote: > >> 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 > >> > > > > > > > > -- > > Rick McNeal > > > > A good friend will come and bail you out of jail ... but, a true > > friend will be sitting next to you saying, "Damn .. that was fun!" > > _______________________________________________ > > storage-discuss mailing list > > [email protected] > > http://mail.opensolaris.org/mailman/listinfo/storage-discuss > > Jim Dunham > Storage Platform Software Group > Sun Microsystems, Inc. > > _______________________________________________ > storage-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/storage-discuss -- Adam Leventhal, FishWorks http://blogs.sun.com/ahl _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
