Since yesterday one of our disk checks reports critical 0MB (0%)
even though there is plenty of space on the disk. Here is the output of df
and the check for the failing mount (file system is btrfs, hence no inode count):
# df -i /mnt/backup-testsystem
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/mapper/vg0-backup--testsystem 0 0 0 - /mnt/backup-testsystem
# df -m /mnt/backup-testsystem
Filesystem 1M-blocks Used Available Use% Mounted on
/dev/mapper/vg0-backup--testsystem 6291456 564844 5726730 9% /mnt/backup-testsystem
# /usr/lib/nagios/plugins/check_disk -c 10% -p /mnt/backup-testsystem
DISK CRITICAL - free space: /mnt/backup-testsystem 0 MB (0% inode=-)];| /mnt/backup-testsystem=564843MB;;5662310;0;6291456
By comparison, same host, different mount works fine:
# df -i /mnt/backup-produktiv/
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/mapper/vg0-backup--produktiv 0 0 0 - /mnt/backup-produktiv
# df -m /mnt/backup-produktiv/
Filesystem 1M-blocks Used Available Use% Mounted on
/dev/mapper/vg0-backup--produktiv 8388608 7196070 1186063 86% /mnt/backup-produktiv
# /usr/lib/nagios/plugins/check_disk -c 10% -p /mnt/backup-produktiv/
DISK OK - free space: /mnt/backup-produktiv 1186062 MB (14% inode=-);| /mnt/backup-produktiv=7196069MB;;7549747;0;8388608
Any ideas what is wrong here? The check worked fine up until yesterday.
Thanks,
Stefan