![](https://secure.gravatar.com/avatar/633ef5db9fa9f929f42531d3ab7b7114.jpg?s=120&d=mm&r=g)
Below is an example of one system (there are quite a few more doing the same thing) that seems to flap between storage sizes 0B and actual size consistently. I am wondering if there are any known issues that may be causing this behavior. The affected systems are VMs running Centos6 on a Centos6 VMhost running KVM.
Any ideas???
Thanks in advance!
2017-05-25 13:40:13 scaleout7 https://mon.asf.alaska.edu/device/device=27/tab=logs/section=eventlog/ /tmp https://mon.asf.alaska.edu/device/device=27/tab=health/metric=storage/ Storage size changed: 0B -> 265GB (/tmp) 2017-05-25 13:40:13 scaleout7 https://mon.asf.alaska.edu/device/device=27/tab=logs/section=eventlog/ /home https://mon.asf.alaska.edu/device/device=27/tab=health/metric=storage/ Storage size changed: 0B -> 4.68GB (/home) 2017-05-25 13:40:13 scaleout7 https://mon.asf.alaska.edu/device/device=27/tab=logs/section=eventlog/ /boot https://mon.asf.alaska.edu/device/device=27/tab=health/metric=storage/ Storage size changed: 0B -> 476MB (/boot) 2017-05-25 13:40:13 scaleout7 https://mon.asf.alaska.edu/device/device=27/tab=logs/section=eventlog/ / https://mon.asf.alaska.edu/device/device=27/tab=health/metric=storage/ Storage size changed: 0B -> 15.2GB (/) 2017-05-25 13:37:54 scaleout7 https://mon.asf.alaska.edu/device/device=27/tab=logs/section=eventlog/ /tmp https://mon.asf.alaska.edu/device/device=27/tab=health/metric=storage/ Storage size changed: 265GB -> 0B (/tmp) 2017-05-25 13:37:54 scaleout7 https://mon.asf.alaska.edu/device/device=27/tab=logs/section=eventlog/ /home https://mon.asf.alaska.edu/device/device=27/tab=health/metric=storage/ Storage size changed: 4.68GB -> 0B (/home) 2017-05-25 13:37:54 scaleout7 https://mon.asf.alaska.edu/device/device=27/tab=logs/section=eventlog/ /boot https://mon.asf.alaska.edu/device/device=27/tab=health/metric=storage/ Storage size changed: 476MB -> 0B (/boot) 2017-05-25 13:37:54 scaleout7 https://mon.asf.alaska.edu/device/device=27/tab=logs/section=eventlog/ / https://mon.asf.alaska.edu/device/device=27/tab=health/metric=storage/ Storage size changed: 15.2GB -> 0B (/)
2017-05-25 13:35:15 scaleout10 https://mon.asf.alaska.edu/device/device=30/tab=logs/section=eventlog/ /tmp https://mon.asf.alaska.edu/device/device=30/tab=health/metric=storage/ Storage size changed: 0B -> 265GB (/tmp) 2017-05-25 13:35:15 scaleout10 https://mon.asf.alaska.edu/device/device=30/tab=logs/section=eventlog/ /home https://mon.asf.alaska.edu/device/device=30/tab=health/metric=storage/ Storage size changed: 0B -> 4.68GB (/home) 2017-05-25 13:35:15 scaleout10 https://mon.asf.alaska.edu/device/device=30/tab=logs/section=eventlog/ /boot https://mon.asf.alaska.edu/device/device=30/tab=health/metric=storage/ Storage size changed: 0B -> 476MB (/boot) 2017-05-25 13:35:15 scaleout10 https://mon.asf.alaska.edu/device/device=30/tab=logs/section=eventlog/ / https://mon.asf.alaska.edu/device/device=30/tab=health/metric=storage/ Storage size changed: 0B -> 15.2GB (/) 2017-05-25 13:32:09 scaleout10 https://mon.asf.alaska.edu/device/device=30/tab=logs/section=eventlog/ /tmp https://mon.asf.alaska.edu/device/device=30/tab=health/metric=storage/ Storage size changed: 265GB -> 0B (/tmp) 2017-05-25 13:32:09 scaleout10 https://mon.asf.alaska.edu/device/device=30/tab=logs/section=eventlog/ /home https://mon.asf.alaska.edu/device/device=30/tab=health/metric=storage/ Storage size changed: 4.68GB -> 0B (/home) 2017-05-25 13:32:09 scaleout10 https://mon.asf.alaska.edu/device/device=30/tab=logs/section=eventlog/ /boot https://mon.asf.alaska.edu/device/device=30/tab=health/metric=storage/ Storage size changed: 476MB -> 0B (/boot) 2017-05-25 13:32:09 scaleout10 https://mon.asf.alaska.edu/device/device=30/tab=logs/section=eventlog/ / https://mon.asf.alaska.edu/device/device=30/tab=health/metric=storage/ Storage size changed: 15.2GB -> 0B (/)