All of lore.kernel.org
 help / color / mirror / Atom feed
From: chris procter <chris-procter@talk21.com>
To: Milan Broz <mbroz@redhat.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] alternative to pvmove on root volume
Date: Fri, 29 Jan 2010 21:18:27 +0000 (GMT)	[thread overview]
Message-ID: <65896.70817.qm@web87106.mail.ird.yahoo.com> (raw)
In-Reply-To: <4B632DE7.80606@redhat.com>

> On 01/29/2010 07:26 PM, chris procter wrote:

> > Unfortuately this project is mostly RHEL4 boxes (its an old SAN, nothing new 
> has been added to it in a couple of years)
> > and so thats what I've been testing with (RHEL4.5 to be precise) so if you 
> really want me too
> > I'll file a bug but I'm pretty sure it will just get closed with "upgrade to a 
> modern version of lvm" :)
> 
> Ah so. Pretty old lvm2 version there. 

Yep, but upgrading means all sorts of risk assessments and revalidating of custom and third party code. I'd much prefer just to reinstall the whole thing onto the new san as RHEL5.4 but thats not going to happen this year :(


>But both RHEL5 and RHEL4 share the same codebase, just upgrade to RHEL4.8.
> (you can even use statically linked lvm binary from newer version if you cannot 
> upgrade...)
> 
> Milan

Using a version of lvm.static copied over is not something I'd considered, but it sounds like a much nicer approach then mine. I'll test it out and report back

Thanks a lot :)

chris


      

      reply	other threads:[~2010-01-29 21:18 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
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 [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=65896.70817.qm@web87106.mail.ird.yahoo.com \
    --to=chris-procter@talk21.com \
    --cc=linux-lvm@redhat.com \
    --cc=mbroz@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.