Thanks Andrew - I couldn't remember the exact wording :)
On Fri, Jan 23, 2009 at 5:53 PM, <[email protected]> wrote: > well, the -V actually tells zfs to make a "volume"... which is > effectively what your "virtual block dev" phrase is saying... but.. > i think ("V" == volume) is more "readable". > > eg, > > # zfs list -t volume > NAME USED AVAIL REFER MOUNTPOINT > mypool/myvol 2M 22.8M 16K - > mypool/vol 64M 84.8M 16K - > > > from zfs admin guide: > > "A ZFS volume is a dataset that represents a block device and can > be used like any block device. ZFS volumes are identified as devices > in the /dev/zvol/{dsk,rdsk}/path directory." > > > On 01/23/09 16:30, Blake wrote: >> >> This is because iSCSI is a block-level protocol. It needs to 'talk' >> directly to blocks. The -V option tell zfs to create a virtual block >> device. Once you connect to it over iSCSI, you can format it like you >> would any block device. >> >> If you want to connect to a zfs filesystem (instead of block device), >> you need to do so with something like NFS or CIFS. >> >> >> >> On Wed, Jan 21, 2009 at 8:18 PM, Billy <[email protected]> wrote: >>> >>> Could this be a bug? >>> >>> If you try creating a filesystem without the -V switch, then iscsi >>> shareing does not work right for that filesystem. >>> >>> I tried it again and now I'm positive that if you don't set a size for >>> you new filesystem, then shareing it over iscsi does not work although the >>> zfs command does not return an error. >>> >>> Anyway, I'm just shareing info... >>> -- >>> This message posted from opensolaris.org >>> _______________________________________________ >>> opensolaris-help mailing list >>> [email protected] >>> >> _______________________________________________ >> opensolaris-help mailing list >> [email protected] > _______________________________________________ opensolaris-help mailing list [email protected]
