Adam Leventhal wrote:
On Thu, Nov 02, 2006 at 12:10:06AM -0800, eric kustarz wrote:
Like the 'sharenfs' property, 'shareiscsi' indicates if a ZVOL should
be exported as an iSCSI target. The acceptable values for this
property
are 'on', 'off', and 'direct'. In the future, we
On Thu, Nov 02, 2006 at 12:10:06AM -0800, eric kustarz wrote:
> > Like the 'sharenfs' property, 'shareiscsi' indicates if a ZVOL should
> > be exported as an iSCSI target. The acceptable values for this
> > property
> > are 'on', 'off', and 'direct'. In the future, we may support o
Adam Leventhal wrote:
Rick McNeal and I have been working on building support for sharing ZVOLs
as iSCSI targets directly into ZFS. Below is the proposal I'll be
submitting to PSARC. Comments and suggestions are welcome.
Adam
---8<---
iSCSI/ZFS Integration
A. Overview
The goal of this projec
On Wed, Nov 01, 2006 at 12:22:46PM -0500, Matty wrote:
> This is super useful! Will ACLs and aliases be stored as properties? Could
> you post the list of available iSCSI properties to the list?
We're still investigating ACL and iSNS support. The alias name will always be
the name of the dataset,
On Wed, 1 Nov 2006, Adam Leventhal wrote:
Rick McNeal and I have been working on building support for sharing ZVOLs
as iSCSI targets directly into ZFS. Below is the proposal I'll be
submitting to PSARC. Comments and suggestions are welcome.
Adam
---8<---
iSCSI/ZFS Integration
A. Overview
T
> I'm assuming that growing the backing-store will be transparent, say
> increasing a target from 500GB to 1TB.
Yes, if you were to set the 'volsize' property, that change would show up
in the target:
# iscsitadm list target -v
Target: pool/volumes/vol1
iSCSI Name: iqn.1986-03.com.sun:02:4db
