Hi,
We installed RMA agent v1.25 on our Esx v3.02 server host.
The RMA agents works.
We try to monitor free disk (/volumes/disk1 for example) space via unc path.
The value that is returned by RMA Agent as being free space is slightly different than the value the OS (VMWARE ESX v3.02) returns.
Rma returns free space of 122 GB but the OS returns only 96 GB.
Who knows ?
Linux (VMWARE 3.02) UNC incorrect disk space result
-
- Posts: 2832
- Joined: Tue May 16, 2006 4:41 am
- Contact:
Hi ALex,
Thanx for your quick answer.
Our corporate policy does not allow access to our systems by foreign (unknown) companies..but....
The good stuff is my collegue made a workaround.
The problem is that the command you mentioned (statfs) is not known in VMWARE ESX 3.x .
Workaround:
Use a shell script as test method to check the free space of your LUNs:
#!/bin/sh
if [ $# -ge 1 ]
then
OS=`uname`
case $OS in
Linux) LUNFREE=`vdf -h | grep $1 | awk '{printf "%d\n",$3}'`;;
*) echo 'ScriptRes:Unknown:script is not designed for '$OS
exit;;
esac
if [ $LUNFREE -gt $1 ]
then
echo "ScriptRes:Bad:"$LUNFREE
else
echo "ScriptRes:Ok:"$LUNFREE
fi
else
echo 'ScriptRes:Unknown:not enough parameters specified'
fi
Thanx for your quick answer.
Our corporate policy does not allow access to our systems by foreign (unknown) companies..but....
The good stuff is my collegue made a workaround.
The problem is that the command you mentioned (statfs) is not known in VMWARE ESX 3.x .
Workaround:
Use a shell script as test method to check the free space of your LUNs:
#!/bin/sh
if [ $# -ge 1 ]
then
OS=`uname`
case $OS in
Linux) LUNFREE=`vdf -h | grep $1 | awk '{printf "%d\n",$3}'`;;
*) echo 'ScriptRes:Unknown:script is not designed for '$OS
exit;;
esac
if [ $LUNFREE -gt $1 ]
then
echo "ScriptRes:Bad:"$LUNFREE
else
echo "ScriptRes:Ok:"$LUNFREE
fi
else
echo 'ScriptRes:Unknown:not enough parameters specified'
fi
-
- Posts: 2832
- Joined: Tue May 16, 2006 4:41 am
- Contact:
Actually, statfs() is an API function, not command line utility. Anyway, script looks great. Thank you for posting it. Probably, it helps other customers.mbulles01 wrote:The good stuff is my collegue made a workaround.
The problem is that the command you mentioned (statfs) is not known in VMWARE ESX 3.x .
Workaround:
Use a shell script as test method to check the free space of your LUNs:
Regards,
Max