This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-bugs] [Bug 487] No space left on device, while writing /local/domai

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 487] No space left on device, while writing /local/domain/0/backend/vbd/113/2050/domain
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Mon, 20 Feb 2006 15:23:49 +0000
Delivery-date: Mon, 20 Feb 2006 15:49:16 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

------- Additional Comments From matta@xxxxxxxxxxxx  2006-02-20 15:23 -------
Yes I am running many domains.  I believe the peak is 55 on a single host. 
Average is 40-50.  It depends on what size plans are ordered and placed on a
specific host node. Ewan is familiar with my setup a bit and he has been on a
host node so you may want to discuss with him.  He does have a corrupt tdb file
I believe.

No I do not have a test case.  It definitely appears to happen more frequently
on new servers where users are still "playing" with their virtual machines and
hence there are many more xm create/shutdown/destroy/sysrq commands being 

Yes I am doing many xm commands in parallel.  For my service users have access
to a control panel where they can perform reboots, etc so in theory 50 xm
creates could all be performed at the same time.

I do not know Python at all so I don't know how much help I can be (I'm a
Perl/PHP guy). I am looking in tdb_store function and I see it IS locked at what
looks to be the most proper places. A few comments.

- This indicates that perhaps invalid values are being sent to tdb_store and
better error checking on the variables themselves to make sure they comform to
what is expected needs to be done.
- tdb_store may not be the problem, the tdb_delete_hash, tdb_nextkey, etc may
need to be locked earlier / later in the code.
- a modification that is attempted fails due to the store being locked, while
the hypervisor itself has already done it's work. I am not so sure on this one
as I don't know what order things are done in or if a store manipulation that
fails due to a locked tdb fails or keeps on re-trying until it gains the lock.

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>