From: Peri Hankey <mpah@thegreen.co.uk>
To: Michael Vrable <mvrable@cs.ucsd.edu>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: Automation scripts
Date: Tue, 28 Sep 2004 09:23:50 +0100 [thread overview]
Message-ID: <41591F96.1030402@thegreen.co.uk> (raw)
In-Reply-To: <20040927151829.A22709@cs.ucsd.edu>
My experience (LVM2.2.00.24 - Mandrake 10.0 - 2.6.8.1-xen0) has been
that when lvm2 runs out of memory (particularly when creating a new
snapshot of an original that already has other snaphots against it) the
whole lvm system with any xenU domains based on it becomes unusable
until the xen0 system is rebooted. Has lvm2 behaved better for you in
that kind of circumstance?
Other than that, from a short acquaintance it looks as if it should be good.
-- Peri
Michael Vrable wrote:
>On Tue, Sep 28, 2004 at 09:50:06AM +1200, Paul Dorman wrote:
>
>
>>Another little query about the LVM stuff: I'm using kernel 2.6 so does this
>>rule out the LVM option? The package note for Sarge's LVM2 says that it works
>>with 2.4 only.
>>
>>
>
>I'm using LVM2 from Sarge (a few weeks out of date now) and a 2.6.8.1
>kernel on Xen. Everything works just fine. (Except for the occasional
>out-of-memory conditions when using many snapshots...)
>
>--Michael Vrable
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
>Project Admins to receive an Apple iPod Mini FREE for your judgement on
>who ports your project to Linux PPC the best. Sponsored by IBM.
>Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/xen-devel
>
>
>
>
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
next prev parent reply other threads:[~2004-09-28 8:23 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-27 19:23 Automation scripts Paul Dorman
2004-09-27 20:26 ` Paul Dorman
2004-09-27 21:53 ` Mark A. Williamson
2004-09-28 14:21 ` Brian Wolfe
2004-09-29 10:36 ` Christian Limpach
2004-09-29 19:47 ` Paul Dorman
2004-09-29 20:23 ` Ian Pratt
2004-09-27 21:46 ` Mark A. Williamson
2004-09-27 21:50 ` Paul Dorman
2004-09-27 22:08 ` Ian Pratt
2004-09-27 22:18 ` Michael Vrable
2004-09-27 22:43 ` Paul Dorman
2004-09-28 18:41 ` Michael Vrable
2004-09-28 8:23 ` Peri Hankey [this message]
2004-09-28 12:26 ` Ian Pratt
2004-09-28 14:55 ` Peri Hankey
2004-09-28 15:43 ` Ian Pratt
2004-09-28 18:09 ` LVM Snapshot Troubles Michael Vrable
2004-09-28 20:06 ` Ian Pratt
2004-09-28 20:52 ` Michael Vrable
2004-09-28 21:23 ` Ian Pratt
2004-09-29 8:39 ` Keir Fraser
2004-09-30 21:02 ` Michael Vrable
2004-09-28 23:59 ` Automation scripts Mark A. Williamson
2004-09-30 20:58 ` Loop and ENBD device management (was Re: Automation scripts) Mark A. Williamson
2004-09-30 21:00 ` Mark A. Williamson
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=41591F96.1030402@thegreen.co.uk \
--to=mpah@thegreen.co.uk \
--cc=mvrable@cs.ucsd.edu \
--cc=xen-devel@lists.sourceforge.net \
/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.