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
On Nov 18, 2009, at 8:54 PM, Duncan Bradey wrote:
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
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
On Nov 18, 2009, at 7:28 PM, Duncan Bradey wrote:
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
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
