Ross wrote:
> Bleh, found out why they weren't appearing. I was just creating a regular
> ZFS filesystem and setting shareiscsi=on. If you create a volume it works
> fine...
>
> I wonder if that's something that could do with being added to the
> documentation for shareiscsi? I can see now that all the examples of how to
> use it are using the "zfs create -V" command, but can't find anything that
> explicitly states that shareiscsi needs a fixed size volume.
>
> Should ZFS generate an error if somebody tries to set shareiscsi=on for a
> filesystem that doesn't support that property?
My initial reaction was yes, however there is a case where you want to
set shareisci=on for a filesystem. Setting it on a filesystem allows
for it to be inherited by any volumes created below that point in the
hierarchy.
Lets take this fictional, but reasonable, dataset hierarchy.
tank/volumes/template/solaris
tank/volumes/template/linux
tank/volumes/template/windows
tank/volumes/archive/
tank/volumes/active/host-abc
tank/volumes/active/host-xyz
tank is the pool name.
volumes is a dataset (with canmount=false if you like)
template, archive, active are allso datasets (again canmount=false)
The actual volumes are: solaris, linux, windows, host-abc, host-xyz
So where do we a turn on iscsi sharing ? It could be done at the
individual volume layer, or it could be done up at the "volumes" dataset
layer eg:
zfs set shareiscsi=on tank/volumes/template/solaris
zfs set shareiscsi=on tank/volumes/template/linux
zfs set shareiscsi=on tank/volumes/template/windows
...
or just do:
zfs set shareiscsi=on tank/volumes/
Aside: having canmount=false on tank/volumes may or may not be a good
idea but it depends on the local deployment.
--
Darren J Moffat
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
