On Dec 22, 2011, at 8:14 AM, Bob Friesenhahn wrote: > On Thu, 22 Dec 2011, Milan Jurik wrote: >> >> Do you want to have big warning to every setup which can be problematic >> in some cases and in some not? In such case you will have warning in too >> many places. > > There could be a warning in the case where the system RAM + L2ARC is > considered to be dangerously small for the size of the pool. Of course this > would need to be based on common estimates since some pools will deduplicate > much better than others.
We have implemented these checks in NexentaStor. It can have unintended consequences, such as a reactive admin destroying the deduped dataset because they didn't read or understand the report completely. This, in turn, leads to the protections added to NexentaStor to prevent destroying deduped datasets. There is other low hanging fruit that will be more effective, IMHO. For example, we are also bumping up the default metadata limit. -- richard -- Richard Elling, Senior Director of Solutions Engineering [email protected] +1-760-896-4422 ------------------------------------------- illumos-discuss Archives: https://www.listbox.com/member/archive/182180/=now RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175430-2e6923be Modify Your Subscription: https://www.listbox.com/member/?member_id=21175430&id_secret=21175430-6a77cda4 Powered by Listbox: http://www.listbox.com
