From: Scott Garron <xen-devel@sce.pridelands.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Daniel Stodden <daniel.stodden@citrix.com>
Subject: Re: Making snapshot of logical volumes handling HVM domU causes OOPS and instability
Date: Sat, 11 Sep 2010 15:16:16 -0400 [thread overview]
Message-ID: <4C8BD580.1020504@sce.pridelands.org> (raw)
In-Reply-To: <4C8116EE.9030204@goop.org>
Scott Garron wrote:
>> dom0 console and HVM domUs would periodically hang for several
>> seconds and then return as if nothing was wrong. [.snip.] I ended
>> up fixing it by unsetting CONFIG_NO_HZ in the kernel
Jeremy Fitzhardinge wrote:
> What kernel is this? This sounds like a symptom of the sched_clock
> problem I fixed a few weeks ago.
2.6.32.18
ref: refs/heads/xen/stable-2.6.32.x
git log shows this as the most recent commit (from Aug 30):
commit 2968b258b1ca6bd16d758dd68900669419caff2b
>> It could just be slightly different architecture or the fact that
>> the machine has overall less RAM (4G instead of 8G).
>
> What happens if you boot that system with "mem=4G"
I managed to finally be able to try this last night, and it didn't seem
to make any difference. It did seem to last a bit longer (I had it
creating and removing snapshots every 6 seconds while the backup process
was also creating and removing them as needed, and it went along for
about 20 minutes before becoming unstable). The OOPS message was
different than last time, but similar to the first one I sent when
reporting this.
After it crashed, I also went ahead and flashed the BIOS to the latest
version, to see if it made any difference. After flashing, I booted
normally (without mem=4G), and got it to crash again - this time with a
similar OOPS message to the one I sent to you in my previous e-mail.
The new BIOS didn't help, obviously. I've appended the ps -eH
-owchan,nwchan,cmd outputs and kernel OOPS messages from last night to
the end of the text file at:
http://www.pridelands.org/~simba/hurricane-server.txt
>> udevd: worker did not accept message -1 (Connection refused) kill
>
> Are they atypical?
I don't recall seeing them before, but after flashing the BIOS, they are
no longer occurring.
>> This post seems to be eerily similar to the problem I'm
>> experiencing. http:[...]xen-devel/2010-09/msg00169.html
>
> Aside from udev being involved, the symptom looks quite different.
I suppose that's true, but he mentions in this post:
http://lists.xensource.com/archives/html/xen-devel/2010-09/msg00286.html
that lvcreate and udev are hanging while creating a snapshot volume.
That's the reason I thought it was similar. (That, and he seems to do
backups in a similar way that I do: creates a snapshot, makes a copy of
the snapshot [although, he block-attaches the volume to a domU to do it
whereas I just use dom0], then removes the snapshot.)
--
Scott Garron
next prev parent reply other threads:[~2010-09-11 19:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-28 1:22 Making snapshot of logical volumes handling HVM domU causes OOPS and instability Scott Garron
2010-08-30 16:52 ` Jeremy Fitzhardinge
2010-08-30 18:18 ` Scott Garron
2010-09-12 9:33 ` J. Roeleveld
2010-08-30 19:13 ` Daniel Stodden
2010-08-30 20:30 ` Scott Garron
2010-08-31 9:20 ` Daniel Stodden
2010-08-31 18:06 ` Scott Garron
2010-09-03 8:06 ` Scott Garron
2010-09-12 9:41 ` J. Roeleveld
2010-09-12 18:48 ` Scott Garron
2010-09-13 0:15 ` Making snapshot of logical volumes handling HVM domUcauses " James Harper
2010-09-13 8:35 ` J. Roeleveld
2010-09-13 8:33 ` Making snapshot of logical volumes handling HVM domU causes " J. Roeleveld
[not found] ` <4C80ABA6.6000203@pridelands.org>
2010-09-03 15:40 ` Jeremy Fitzhardinge
2010-09-11 19:16 ` Scott Garron [this message]
2010-09-12 0:20 ` Making snapshot of logical volumes handling HVM domUcauses " James Harper
2010-08-31 6:59 ` Making snapshot of logical volumes handling HVM domU causes " Xu, Dongxiao
2010-08-31 8:16 ` Scott Garron
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=4C8BD580.1020504@sce.pridelands.org \
--to=xen-devel@sce.pridelands.org \
--cc=daniel.stodden@citrix.com \
--cc=jeremy@goop.org \
--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.