You have it opposite. Best practice says the Aggregate threshold max usage should be 80% for best performance, 90% at most. The reasoning is Data ONtap has to search much harder to find free blocks to write with, thus CPU / other resources are consumed in this search.
FlexVols at 100% usage do not have any detrimental impact other than running out of space or throwing filer/dfm alerts, so I like to keep those at 95% or less if they contain static block-level data.
You should reduce the usage of your aggregate immediately!
HTH,
Hadrian
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Paul Letta Sent: Thursday, January 31, 2008 7:25 AM 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