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	/tmp	Storage size changed: 0B -> 265GB (/tmp)
	2017-05-25 13:40:13	scaleout7	/home	Storage size changed: 0B -> 4.68GB (/home)
	2017-05-25 13:40:13	scaleout7	/boot	Storage size changed: 0B -> 476MB (/boot)
	2017-05-25 13:40:13	scaleout7	/	Storage size changed: 0B -> 15.2GB (/)
	2017-05-25 13:37:54	scaleout7	/tmp	Storage size changed: 265GB -> 0B (/tmp)
	2017-05-25 13:37:54	scaleout7	/home	Storage size changed: 4.68GB -> 0B (/home)
	2017-05-25 13:37:54	scaleout7	/boot	Storage size changed: 476MB -> 0B (/boot)
	2017-05-25 13:37:54	scaleout7	/	Storage size changed: 15.2GB -> 0B (/)
	2017-05-25 13:35:15	scaleout10	/tmp	Storage size changed: 0B -> 265GB (/tmp)
	2017-05-25 13:35:15	scaleout10	/home	Storage size changed: 0B -> 4.68GB (/home)
	2017-05-25 13:35:15	scaleout10	/boot	Storage size changed: 0B -> 476MB (/boot)
	2017-05-25 13:35:15	scaleout10	/	Storage size changed: 0B -> 15.2GB (/)
	2017-05-25 13:32:09	scaleout10	/tmp	Storage size changed: 265GB -> 0B (/tmp)
	2017-05-25 13:32:09	scaleout10	/home	Storage size changed: 4.68GB -> 0B (/home)
	2017-05-25 13:32:09	scaleout10	/boot	Storage size changed: 476MB -> 0B (/boot)
	2017-05-25 13:32:09	scaleout10	/	Storage size changed: 15.2GB -> 0B (/)