Concerning the reservations, here's a snip from "man zfs":
The reservation is kept equal to the volume's logical
size to prevent unexpected behavior for consumers.
Without the reservation, the volume could run out of
space, resulting in undefined behavior or data corrup-
tion, depending on how the volume is used. These effects
can also occur when the volume size is changed while it
is in use (particularly when shrinking the size).
Extreme care should be used when adjusting the volume
size.
Though not recommended, a "sparse volume" (also known as
"thin provisioning") can be created by specifying the -s
option to the zfs create -V command, or by changing the
reservation after the volume has been created. A "sparse
volume" is a volume where the reservation is less then
the volume size. Consequently, writes to a sparse volume
can fail with ENOSPC when the pool is low on space. For
a sparse volume, changes to volsize are not reflected in
the reservation.
Did you do anything like this?
HTH,
//Jim
--
This message posted from opensolaris.org
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
