Description of problem: Engine raises a warning that free space in /var/run/vdsm is less than 1G. But /var/run is mounted as a tmpfs. By default, the maximum size is half of the total physical memory. The warning is misleading because people could find it still have a lot of free space on the disk filesystem. And 1g shouldn't be a low threshold for memory. So it seems we needn't monitor the usage of '/var/run/vdsm' in 'diskStats' since it could be covered by memory usage monitoring. Version-Release number of selected component (if applicable): vdsm-4.10.3-6.fc18.src.rpm How reproducible: 100% Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I think that this is better solved on the Engine side, by lowering the threshold for /var/run/vdsm. We would like to keep monitoring that that directory exists and has *some* free space (both for Fedora and EL6).
(In reply to Dan Kenigsberg from comment #1) > I think that this is better solved on the Engine side, by lowering the > threshold for /var/run/vdsm. We would like to keep monitoring that that > directory exists and has *some* free space (both for Fedora and EL6). Dan, can you recommend the value to be changed please?
/var/run/vdsm contains tiny .pid files, smalle .recovery files, soft links, etc. I think that 100MiB would be enough for a big production server.
This is an automated message. Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.
This is an automated message: This bug has been re-targeted from 3.4.2 to 3.5.0 since neither priority nor severity were high or urgent. Please re-target to 3.4.3 if relevant.
This bug was fixed and is slated to be in the upcoming version. As we are focusing our testing at this phase on severe bugs, this bug was closed without going through its verification step. If you think this bug should be verified by QE, please set its severity to high and move it back to ON_QA