All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter <p.xensource.com@rimuhosting.com>
To: Ewan Mellor <ewan@xensource.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Loop Back Mounted Files Cannot be UMounted, DomU Cannot Restart
Date: Wed, 14 Mar 2007 14:28:26 +1300	[thread overview]
Message-ID: <45F74FBA.5090301@rimuhosting.com> (raw)
In-Reply-To: <20070313100540.GE30259@leeni.uk.xensource.com>


Ewan Mellor wrote:
>> [2007-03-08 21:53:48 xend 19559] DEBUG (XendDomain:198) Cannot recreate
>> information for dying domain 163.  Xend will ignore this domain from now on.
> 
> This looks suspicious too.  It looks like you have a VM that has not been
> properly cleaned up -- presumably it's the one that's holding your loopback
> device open.  Do you have the logs for what happened to domain 163?
> 
> Ewan.
> 

Did you have any particular logs in mind?

I think it was likely just from an xm destroy.  Though an xm destroy 
does not always lead to this problem.

Anyway to recover from this?  Force Xen to release the loop back mounted 
file:/ device?

Recap on our environment: Centos4, hotplug, loop back mounted files, 
about 60 odd domUs, "page allocation failure" errors (typically with 
networking code in the stack dump), xen 3.0.3, sometimes it seems like 
the problem is triggered when there is high disk io load.

Any ideas or suggestions appreciated.

Regards, Peter

      reply	other threads:[~2007-03-14  1:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-12 23:43 Loop Back Mounted Files Cannot be UMounted, DomU Cannot Restart Peter
2007-03-13 10:05 ` Ewan Mellor
2007-03-14  1:28   ` Peter [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45F74FBA.5090301@rimuhosting.com \
    --to=p.xensource.com@rimuhosting.com \
    --cc=ewan@xensource.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.