Hi Anna, Markus
It was the incorrect restrict clause referencing the FQDN of the server, and
not the GPFS daemon node name, that was causing the problem. This has now been
updated and we have nice graphs
Many thanks!
Richard
___
gpfsug-discuss
ain discussion list
Date: 11/10/2018 14:10
Subject: Re: [gpfsug-discuss] Performance collector no results for
Capacity
Sent by:gpfsug-discuss-boun...@spectrumscale.org
Anna,
Yes, that will be it! I was running the wrong command as you surmise.
The GPFSFileSetQuota
t;
mailto:r.so...@imperial.ac.uk>>
To: "'gpfsug-discuss@spectrumscale.org'"
mailto:gpfsug-discuss@spectrumscale.org>>
Date:10/10/2018 17:43
Subject:[gpfsug-discuss] Performance collector no results for Capacity
Sent by:
gpfsug-discuss-boun...@s
itz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart,
HRB 243294
From: "Sobey, Richard A"
To: "'gpfsug-discuss@spectrumscale.org'"
Date: 10/10/2018 17:43
Subject:[gpfsug-discuss] Performance collector no results for
Capacity
Sent by:
Hi all,
Maybe I'm barking up the wrong tree but I'm debugging why I don't get a nice
graph in the GUI for fileset capacity, even though the GUI does know about
things such as capacity and inodes and usage.
So off I go to the CLI to run "mmperfmon query GPFSFilesetQuota" and I get this:
Oct-10
