2010-06-22 10:16 AM
So I resized my vol0 down from 522G to 500G on all my filers, and I got this on one of them:
Tue Jun 22 08:33:25 PDT [filer2: perf.archive.max_disk_space.changed:info]:
Maximum disk space consumption allowed for the performance archiver was
changed from '14422869361' to '10737418241' bytes. Change not committed.
Is there any way to set Performance Archiver's max disk space consumption or is this a hard setting in the system?
Solved! SEE THE SOLUTION
2010-06-24 06:02 PM
You are correct, sorry I must've fat fingered the first time I tried it.
Anyway, I think it resolved itself because the stats directory on that filer has since shrunk.
2012-09-18 08:08 AM
Hi! I had the same message from our FAS3240 when resize the root volume:
perf.archive.max_disk_space.changed:info]: Maximum disk space consumption allowed for the performance archiver was changed from '7112916829' to '565127332' bytes. Change not committed.
What is the performance archiver ? and Which can change with this setting ?
Any recomendations ?
2012-09-19 12:12 AM
NetApp collects detailed performance stats (with second resolution) by default. This is large amount of data so it will automatically delete older stats when consumed space exceeds threshold. Threshold is computed as percentage of root volume size which explains why it changes when root volume is resized.
There is KB article about performance archiver, I do not remember exact number.