On Wed, May 23, 2012 at 03:50:28AM -0400, Eyal Edri wrote:
only change i see from vdsm is this:
Change to use WatchedFileHandler instead of FileHandler in logger.conf (details)
That's absolutely unrelated. I was refering to whether the Jenkins server was rebooted or fixed in some other means?
e
----- Original Message -----
From: "Dan Kenigsberg" danken@redhat.com To: "ShaoHe Feng" shaohef@linux.vnet.ibm.com, eedri@redhat.com Cc: "VDSM Project Development" vdsm-devel@lists.fedorahosted.org, "Adam Litke" agl@us.ibm.com, "Mark Wu" wudxw@linux.vnet.ibm.com, "shu ming" shuming@linux.vnet.ibm.com, "Xu He Jie" xuhj@linux.vnet.ibm.com Sent: Tuesday, May 22, 2012 10:52:41 PM Subject: Re: vdsm unit test error
On Tue, May 22, 2012 at 05:02:01PM +0800, ShaoHe Feng wrote:
both mountTests and parted_utils_tests failed.
Failed where? On your own host? Is it reproducible? We had a similar, but transient, problem in http://jenkins.ovirt.org/job/vdsm_unit_tests/143/console
We, or some other suite using the server, may be leaking a loop device. Eyal Edri, do you know what has made this go away in run #144?
the test execute 'mount' and 'umount' command. after the umount command, the loop device can not be freed
here is the log:
-------------------- >> begin captured logging <<
Storage.Misc.excCmd: DEBUG: 'dd if=/dev/zero of=/tmp/tmpH2KSCr bs=100M count=1' (cwd None) Storage.Misc.excCmd: DEBUG: SUCCESS: <err> = '1+0 records in\n1+0 records out\n104857600 bytes (105 MB) copied, 0.266024 s, 39 4 MB/s\n'; <rc> = 0 Storage.Misc.excCmd: DEBUG: 'losetup -f --show /tmp/tmpH2KSCr' (cwd None) Storage.Misc.excCmd: DEBUG: FAILED: <err> = 'losetup: could not find any free loop device\n'; <rc> = 255
--------------------- >> end captured logging <<
Does your Linux host have a trace of the generated loop device? What says losetup -a ?