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-devel] domU oom -> xvda1 read-only without any notice?

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] domU oom -> xvda1 read-only without any notice?
From: Josip Rodin <joy@xxxxxxxxxxxxxx>
Date: Wed, 31 Mar 2010 09:33:40 +0200
Delivery-date: Wed, 31 Mar 2010 00:34:49 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)

Two days ago a resource-intensive process caused one of my new 2.6.32 domUs
to crash and burn, so yesterday I recompiled the kernel with debug options
and retried it. In the early hours of today, after a few hours of running
the same process, the kernel noticed an OOM again and started killing Apache
and PostgreSQL. Unfortunately what also happened was that the root partition
(/dev/xvda1) was somehow marked read-only. I tried to remount it from within
domU, but I just got:

% sudo mount -o remount,rw /
mount: block device /dev/xvda1 is write-protected, mounting read-only

There are no messages in the kernel log on either the .32 domU or the .26
dom0. What do I do, other than shutdown and re-create? How does one manually
'talk' to blkback to see what's up?

     2. That which causes joy or happiness.

Xen-devel mailing list