[ZBX-18869] Disk is overloaded > Created: 2021 Jan 12  Updated: 2021 Jun 10  Resolved: 2021 Jun 10

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Templates (T)
Affects Version/s: 5.0.6
Fix Version/s: None

Type: Problem report Priority: Trivial
Reporter: Enachi Sergiu Assignee: Aleksandrs Petrovs-Gavrilovs
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows Server 2019 Standard (Virtual Machine)


Attachments: PNG File Screenshot 2021-01-12 183449.png     PNG File Screenshot 2021-01-12 183851.png    
Issue Links:
Duplicate
is duplicated by ZBX-19514 Disk utilization Windows template wrong Closed

 Description   

Steps to reproduce:

  1. Each day we have some extensive DB tasks running on the database server during the night
  2. Disk is overloaded (util > {$VFS.DEV.UTIL.MAX.WARN}% for 15m) - is triggered - that is expected
  3. But the operational data is often beyond 100% - how this is possible?..

Result:
See screenshots

Expected:
100% top load



 Comments   
Comment by Alexey Pustovalov [ 2021 Jan 12 ]

It is possible, for example when you use NAS.

Comment by Enachi Sergiu [ 2021 Feb 05 ]

well, the Server is on Cloud based solution, based on VMware vCloud Director. I assume our storage is a LUN from a shared datastore.

If this is the reason for such behavior, the only solution for me then is to disable these items.

 

PS: built in Windows performance monitor never registered more than 100% utilization.

Comment by Dmitry Krupornitsky [ 2021 Apr 26 ]

I have seen such picture on my cloud storage, I should say that was normal and usual thing for high loaded instances. As I got myself, it is due to the fact how information about utilization is processed. Usually the information is gathered in certain intervals, say 1 second. When you've exhausting disk tasks, the intervals can shift to some milliseconds to get things done thus giving some positive gitter. When Zabbix agent processes these values, it gets more or less data in the interval it considers static so it can lower or higher the actual value. I bet you never mentioned lower ones, but higher are obvious.

I suppose you should pay bigger attention to the average values and discard spikes.

Comment by Dmitry Krupornitsky [ 2021 Apr 30 ]

Did you have any extreme values when it is not so loaded?

Comment by Enachi Sergiu [ 2021 May 13 ]

not so sure. It happens daily, multiple times mostly on a secondary DB server, from where most of the reports and backups are generated.

Still, I don't see this behavior on the primary Database server (same OS, same hw, but different psychical location) and it's heavily used, since it does the main job, but it may not have same impact on the disk as much as the secondary.

Comment by Dmitry Krupornitsky [ 2021 Jun 10 ]

Will continue work through https://support.zabbix.com/browse/ZBX-19514

Generated at Sat Aug 02 10:25:38 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.