[EMAIL PROTECTED] wrote on 09/10/2007 12:13:18 PM:
> [EMAIL PROTECTED] wrote: > > Very true, you could even pay people to track down heavy users and > > bonk them on the head. Why is everyone responding with alternate routes to > > a simple need? > > For the simple reason that sometimes it is good to challenge existing > practice and try and find the real need rather than "I need X because > I've always done it using X". I am not against refactoring solutions, but zfs quotas and the lack of user quotas in general either leave people trying to use zfs quotas in lieu of user quotas, suggesting weak end runs against the problem (a cron to calculate hogs), or belittling the need to actually limit disk usage per user id. All of these threads to this point have not answered the needs in anyway close to an solution that user quotas allow. > > We always used a vfstab and dfstab (or exportfs) file before and used a > separate software RAID and filesystem before too. Yes, and the replacements (when talking ZFS) are either parity or better -- that makes switching a win-win. ENOSUCH when talking user quotas. > > > User quotas have been used in the past, and will be used in > > the future because they work (well), are simple, tied into many existing > > workflows/systems and very understandable for both end users and > > administrators. You can come up with 100 other ways to accomplish psudo > > user quotas or end runs around the core issue (did we really have google > > space farming suggested -- we are reading a FS mailing list here?), but > > quotas are tested and well understood fixes to these problems. Just > > because someone decided to call ZFS pool reservations quotas does not mean > > the need for real user quotas is gone. > > Reservations in ZFS are quite different to Quotas, ZFS has both > concepts. A reservation is a guaranteed minimum, a quota in ZFS is a > guaranteed maximum. > Reservations (the general term when talking most of the disk virtualizing and pooling technologies in play today) usually cover both the floor (guaranteed space) and ceiling (max alloc space) for the pool volume, dynamic store, or backing store. ZFS Quotas (reservations) can be called whatever you want -- it has just become frustrating when people start pushing ZFS quotas (reservations) as a drop in replacement for user quotas. They are tools for different issues with some overlap. Even though one can pound in a nail with a screwdriver, I would rather have a hammer. _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
