From: chris procter <chris-procter@talk21.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] alternative to pvmove on root volume
Date: Fri, 29 Jan 2010 18:39:30 +0000 (GMT) [thread overview]
Message-ID: <905780.79489.qm@web87111.mail.ird.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1001290822570.27080@bmsred.bmsi.com>
> On Thu, 28 Jan 2010, malahal@us.ibm.com wrote:
> > given that pvmove also works by mirroring I'm not convinced I haven't
> > just been lucky so far . So does anyone have any ideas or even better
> > experiance on whether this is likely to work or am I setting myself up
> > for a world of pain if I try it on a live server?
>
> Yes, pvmove works very similar. It will create a mirror for each segment
> one at a time, so it may have to create lot more mirrors depending on
> your configuration. If it ends up needing more 'lvconverts' (suspends),
> then the probability of failure (deadlock) will increase.
I've been testing using VMs cloned from the same template, the clones that I used pvmove on have deadlocked maybe 75% of the time, and the ones that I lvconverted have never deadlocked. However given your explanation I think its probable that I've just been lucky and my 10 or so tests haven't had enough 'suspends' to trigger the issue. Oh well back to the planned downtime route.
Thanks for the help :)
chris
next prev parent reply other threads:[~2010-01-29 18:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 20:11 [linux-lvm] alternative to pvmove on root volume chris procter
2010-01-28 21:17 ` malahal
2010-01-29 13:28 ` Stuart D. Gathman
2010-01-29 18:39 ` chris procter [this message]
2010-01-29 9:21 ` Milan Broz
2010-01-29 18:26 ` chris procter
2010-01-29 18:50 ` Milan Broz
2010-01-29 21:18 ` chris procter
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=905780.79489.qm@web87111.mail.ird.yahoo.com \
--to=chris-procter@talk21.com \
--cc=linux-lvm@redhat.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.