Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 615733 - [vdsm] vdsm fails to start if no space left on device but alerts nothing about it
[vdsm] vdsm fails to start if no space left on device but alerts nothing abou...
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm (Show other bugs)
All Linux
low Severity medium
: rc
: ---
Assigned To: Dan Kenigsberg
Depends On:
  Show dependency treegraph
Reported: 2010-07-18 06:41 EDT by Haim
Modified: 2016-04-18 02:33 EDT (History)
6 users (show)

See Also:
Fixed In Version: vdsm-4.9-13.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-08-19 11:15:58 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Haim 2010-07-18 06:41:57 EDT
Description of problem:

vdsm service fails to start (reasonable) when no space left on disk, however, it alerts nothing about it, and when i start service, it says 'ok', however, whet querying for service status it appears down. 
the problem is that no space left on disk, hence, I suggest to add a test to service when it starts. 

this issue found on rhel6, however, i suppose it exists in previous versions. 

this is important, as when it occurs, log cannot be written, so, no actual info why service doesn't start. 

vdsm 4.9-9-10. 


make sure no space left on root partition, and start vdsm
Comment 2 Haim 2010-08-22 02:53:59 EDT
verified, tried to start vdsm service with no success, and got the following message: low space [FAILED]

root@silver-vdse ~]# service vdsmd status
VDS daemon is not running
[root@silver-vdse ~]# service vdsmd start
Starting netconsole...
Server address not specified in /etc/sysconfig/netconsole
Starting iscsid: 
vdsm: low log space                                        [FAILED]


Note You need to log in before you can comment on or make changes to this bug.