Thanks Richard,
I've set the refreservation down and this has "freed" up space, I'm now setting
up a process to monitor and update the refreservation attribute on zfs volumes
used so we can thin provision yet keep some storage (half the remaining volume
size) available to ensure that these volu
Richard,
Thanks for this, this explains why I am seeing this. I am using snapshots as I
am replicating the data to other servers (via zfs send/recieve) is there
another way to prevent this behaviour and still use snapshots? Or do I need to
create these volumes as thin provisioned to get aroun
Guys,
Forgive my ignorance on this but I am wondering how ZFS uses space when a
volume is created with the -V parameter and then shared as an iSCSI lun.
For example, I created 5 volumes 2 * 1TB in size and 3 * 2TB in size, but the
space usage appears to be in addition to this size specification
Rasmus,
I had 4 volumes:-
Found 4 LU(s)
GUIDDATA SIZE SOURCE
---
600144f0b00309004afb990f0004 1099511562240
/dev/zvol/rdsk/infobrick/iscsi/prmel1vspcor-jhgtier2-03
600144f
I am at a loss of where else to look to work out why my vSphere 4 server cannot
access my iSCSI LUNs via the COMSTAR iSCSI target.
# uname -a
SunOS prmel1iscsi01 5.11 snv_111b i86pc i386 i86pc Solaris
# itadm list-target -v
TARGET NAME STATESES
