In a fresh container install on a fresh 3.4 install, df is completely and utterly non-functional.
No errors, just not reporting any disk space in use. (I dumpted 30G of random data to the server to verify this)
[user@mirrors]~% df -h
Filesystem Size Used Avail Use% Mounted on
/dev/simfs 200G 128K 200G 1% /
none 256M 8.0K 256M 1% /dev
none 256M 0 256M 0% /dev/shm
[user@mirrors]~% sudo du -sh /
30G /
Interesting, the same results are obtained when I do df at the proxmox host level:
...
/var/lib/vz/private/103 200G 128K 200G 1% /var/lib/vz/root/103
none 256M 8.0K 256M 1% /var/lib/vz/root/103/dev
none 256M 0 256M 0% /var/lib/vz/root/103/dev/shm
...
Any ideas where to look/how to correct this? In my production environment this would break more than a little of my monitoring...
No errors, just not reporting any disk space in use. (I dumpted 30G of random data to the server to verify this)
[user@mirrors]~% df -h
Filesystem Size Used Avail Use% Mounted on
/dev/simfs 200G 128K 200G 1% /
none 256M 8.0K 256M 1% /dev
none 256M 0 256M 0% /dev/shm
[user@mirrors]~% sudo du -sh /
30G /
Interesting, the same results are obtained when I do df at the proxmox host level:
...
/var/lib/vz/private/103 200G 128K 200G 1% /var/lib/vz/root/103
none 256M 8.0K 256M 1% /var/lib/vz/root/103/dev
none 256M 0 256M 0% /var/lib/vz/root/103/dev/shm
...
Any ideas where to look/how to correct this? In my production environment this would break more than a little of my monitoring...
