[Xen-devel] domU oom -> xvda1 read-only without any notice?

[Josip Rodin <joy@xxxxxxxxxxxxxx>]

Hi,

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
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel