I am one of the much blessed university users who wishes to provide home directories and web space to thousands of users and is being bitten by abysmal scaling behaviour of zfs, the overhead of creating thousands of zfs files sytems in a pool can takes days to complete. Sharing or unsharing them can take hours.
The creation of user and group quotas allows me to create a functional environment but I loose many key zfs features such as snapshot control of an individual's files and easy self service recovery also the flexability in setting share parametes on an individual's filesystem. It is not clear to me how snapshots interact with user and group quotas. The latest ZFS admin guide contains a single line mentioning snapshots and user quotas: However, the user or group quota is applied when a clone or a snapshot is > created from a file system that has a user or group quota. > "applied to a clone" I understand what that means, "applied to a snapshot" - not so clear does it mean enforced on the original dataset? If so how do you delegate the ability for an individual to free blocks charged against quota that are in filesystem wide snapshots? I'm guessing you cannot. I truly hope that effort is being made to resolve the underlying scaling issues but I have not seen any light in the recent "next words" talk. If anyone could point me to discussions where this issue is being driven I'd love to find out. Regards, Alastair
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
