> making transactional,logging filesystems > thin-provisioning aware should be hard to do, as > every new and every changed block is written to a new > location. so what applies to zfs, should also apply to btrfs or > nilfs or similar filesystems. > > i`m not sure if there is a good way to make zfs > thin-provisioning aware/friendly - so you should wait > what a zfs developer has to tell about this.
ZFS already supports thin-provisioning, and has since pretty much the beginning (earliest I've used it in is ZFSv6). I may get the terms backwards here, but if the Quota property is larger than the Reservation, then you have a thin-provisioned volume or filesystem. The Quota will set the "disk size" or "available space" that the OS sees, while the Reservation sets "the currently usable space". As the OS uses space in the volume/fs and approaches the Reservation, you just increase the value. The "total size" that the OS doesn't change, but the actual amount of usable space does. This is especially useful for volumes that are exported via iSCSI. -- This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
