All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Smith <andy@strugglers.net>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Best way to image devices in an LVM environment
Date: Mon, 28 Aug 2006 20:04:56 +0000	[thread overview]
Message-ID: <20060828200456.GT1011@strugglers.net> (raw)
In-Reply-To: <20060828195146.GD16612@dragonhold.org>

[-- Attachment #1: Type: text/plain, Size: 1050 bytes --]

On Mon, Aug 28, 2006 at 08:51:46PM +0100, Graham Wood wrote:
> On Mon, Aug 28, 2006 at 07:48:43PM +0000, Andy Smith wrote:
> > that lvm2 has had pvresize since 2.02.00 so if I upgrade userland
> > tools (my kernel is 2.6.16.19) then would I just need to do a
> > pvresize after expanding the block device that my single pv/vg is
> > on?
> Would it not be easier to just replace with a larger disk - mirror to the same size, and 
> have another partition afterwards.
> 
> You end up with 2pvs (both mirrored, I would expect), rather than the "nicer" answer of a 
> single pv, but as long as the whole thing is then controlled through LVM is there really any 
> loss as a result?

Hmm yes as you say I think I could just make another partition in
the empty space, RAID-1 that, put a PV on the new MD device and then
vgextend onto it I suppose.  It just seems a litlle messy though to
needlessly have the extra partitions and if I can fix it before the
machine is put in production then I feel like I probably should.

Cheers,
Andy

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2006-08-28 20:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-27  4:42 [linux-lvm] Best way to image devices in an LVM environment Andy Smith
2006-08-27  5:20 ` Jim Morgan
2006-08-27  6:16   ` Andy Smith
2006-08-27 11:51     ` Matthew Gillen
2006-08-28 19:48       ` Andy Smith
2006-08-28 19:51         ` Graham Wood
2006-08-28 20:04           ` Andy Smith [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=20060828200456.GT1011@strugglers.net \
    --to=andy@strugglers.net \
    --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.