Thanks Sanjeevb,
By the way, this only seems to fail when I set up a volume instead of a file
system. Should I be setting up a volume in this case, or will a file system
suffice?
If I turn off snapshots for this then it should work. I'll try this.
Regards,
Kevin
--
This message posted from op
Kevin,
Kevin Pattison wrote:
> Hey all,
>
> I'm setting up a ZFS based fileserver to use both as a shared network drive
> and separately to have an iSCSI target to be used as the "Hard disk" of a
> windows based VM runninf on another machine.
>
> I've built the machine, installed the OS, created
I've seen this error often, but mostly the volume is shared.
I think it happens as soon ay the volume has snapshots.
To check if the volume is exposed or not, you can run:
iscsitadm list target -v
If the volume shows up, it's OK and you should ignore the message.
K
--
This message posted from
Hey all,
I'm setting up a ZFS based fileserver to use both as a shared network drive and
separately to have an iSCSI target to be used as the "Hard disk" of a windows
based VM runninf on another machine.
I've built the machine, installed the OS, created the RAIDZ pool and now have a
couple of
