Server Management - Systems Insight Manager
1753734 Members
4409 Online
108799 Solutions
New Discussion юеВ

Re: File System Space Used percentages incorrect

 
Christopher Knight
Frequent Advisor

File System Space Used percentages incorrect

Running management agents 7.6 on HPSIM 5.0 SP5.

Used Space, Unused Space and Total Space read correctly but the Percent Space Used does not compute correctly.

Example...
N:\
Used Space 62529MB
Unused Space 24177MB
Total Space 286706MB

Reads incorrectly as 33% Percent Space Used
It shoud read 91%

Tried restarting Management Agents and restartd server but it still reads the same.

Any idea why the percentages are incorrect on this server?
Christopher Knight
12 REPLIES 12
Christopher Knight
Frequent Advisor

Re: File System Space Used percentages incorrect

Adding attachment.
Christopher Knight
Testo
New Member

Re: File System Space Used percentages incorrect

I am having the same issues.

I'll bump this for an answer!
tmagee
Valued Contributor

Re: File System Space Used percentages incorrect

This posting suggests that a bug has been reintroduced to the 7.6 agents that can display your issue: -

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1064860
Nick Sunley
New Member

Re: File System Space Used percentages incorrect

I have this problem as well. I'm using the latest 7.6 Management Agents for WIndows
Christopher Knight
Frequent Advisor

Re: File System Space Used percentages incorrect

I have a call open with HP about this issue. I will update if they find anything.
Christopher Knight
Terri Harris
Honored Contributor

Re: File System Space Used percentages incorrect

For anyone experiencing this issue - is it with Windows 2000 or Windows 2003?
BoydG
Frequent Visitor

Re: File System Space Used percentages incorrect

2003
Testo
New Member

Re: File System Space Used percentages incorrect

I'm running 2000 at the current time
Christopher Knight
Frequent Advisor

Re: File System Space Used percentages incorrect

Reverting back to agent version 7.51 fixed this issue.

Please bump this issue up in priority.
Christopher Knight