On Aug 9, 2011, at 9:30 AM, Drew Fisher wrote: > Good morning! > > I wanted to discuss 7032205 > (http://monaco.sfbay.sun.com/detail.jsf?cr=7032205) with the group to try to > get a consensus with the right approach to take. What I was thinking was > setting a value of 1% of the total size of the root pool, with an upper bound > of 1gb. > > For the ultra small disks (32gb SSD), 1% is 320MB. For huge disks (2tb HDD), > we'd cap at 1gb. This would provide admins a little bit of breathing room > for a full root pool.
It seems like that's a pretty big chunk to set aside. I know, it's unlikely to matter much that a few GB are wasted, but it seems like a poor default approach. The issue is resolved when there are literally a handful of blocks to complete writes required for the deletion of unwanted files or BEs. Would it be better to set aside a static amount, say 256KB or something? Probably best to make this a tunable in the DTD and UIs, so if someone wants a few GB set aside, they can choose to do so. But, default I'd say a much smaller amount would be better. That said, I'm not sure what granularity there is... I'm fairly certain that all capacity determinations can be used, but it would be kind of lame to convert GB to KB and subtract a small amount in KB and use that value. Pain. I guess this would take some thought. It would be nice if zfs took reverse amounts (set quota to all but this amount), but I don't think it does. > The problem with doing something like this is some admins would really > appreciate the installers doing something like this for them while other > admins want to customize each and every single aspect of their install. This > leads to a few approaches: > > 1: Set up an ICT to do the quota setting *after* we successfully install - > this is so we can complete the install without zfs getting in the way. > > 2: Set up controller.py to add an additional zpool option for the quota on > the root pool. > > 3: other? Add something to the default manifest for AI and force the option > for GUI and TI? DTD entries specifically for this? I prefer setting it along with other ZFS/rpool attributes prior to install. So, a setting in the DTD (with a default) and having it as part of the root disk setup in the GUI/TI. Using a default here I think minimizes the impact of "yet another thing to select" during install, and gives the flexibility that most admins will want. Best Jesse > > Please let me know what you folks think! > > Thanks! > > -Drew > _______________________________________________ > caiman-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/caiman-discuss _______________________________________________ caiman-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
