During update from 7.0 to 7.2 we hit the issue of 100% full aggregate - apparently 7.2 requires more space for metadata which suddenly made aggregate overcommitted and turned off space reservation on some of contained FlexVols. As those hosted LUNs it was not exactly the desired result :)
Resolution was to decrease size of overcommitted FlexVols until space reservation was enabled again. So you may want to leave some safety margin on your aggregate anyway.
С уважением / With best regards / Mit freundlichen Grüβen
--- Andrey Borzenkov Senior system engineer -----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Paul Letta Sent: Thursday, January 31, 2008 6:25 PM To: toasters@mathworks.com Subject: Aggr's at 100% with FlexVols
Hi, I know when traditional vols are in use, you don't want to let them get too close to full because performance will be affected.
But what about using FlexVols and Aggrs ?
I have a few Aggrs that are at 100%. But the FlexVols in those Aggrs are mostly under 50%.
I had a NetApp support person tell me that its bad to have Aggrs at 100%, even if the FlexVols are not full.
What's the answer here. Does having Aggrs at 100% because the FlexVols contained in them are sized to fill the Aggr present a performance issue ?
I would think that as long as the flexvols are not close to full, its ok to have the aggr's at 100%.
Thanks,
Paul