[ZBX-737] Incorrect result from Zabbix Agent about free space for large disks Created: 2009 Feb 24 Updated: 2017 May 30 Resolved: 2009 Mar 02 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Agent (G) |
Affects Version/s: | 1.4.5 |
Fix Version/s: | 1.6 |
Type: | Incident report | Priority: | Minor |
Reporter: | Igor Danoshaites (Inactive) | Assignee: | Unassigned |
Resolution: | Fixed | Votes: | 1 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
Red Hat Enterprise Linux ES release 4 (Nahant Update 4) |
Description |
Hello, I have incorrect result from Zabbix Agent about free space with large disks. Where is the problem, and is there a workaround solution ? Example: [zabbix@linux1 bin]$ df |
Comments |
Comment by Dmitry Borovikov [ 2009 Mar 02 ] |
The reported issue lies not in the work of the agent, but in the bug in the system call "statvfs()" of Linux. To get more details about this bug, follow the link: https://bugzilla.redhat.com/show_bug.cgi?id=189238. This system call returns wrong values for fragments' sizes of NFS partitions. The agent's key "vfs.fs.size" was improved to escape such bugs. Fragments' sizes are not used; besides, fragments are not implemented in Linux at the moment. Thanks for the report, |
Comment by Igor Danoshaites (Inactive) [ 2009 Mar 02 ] |
I close this issue. Original reporter of this issue has been notified by mail. |