All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Waldo <pwaldo@waldoware.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Unable to add new drive to LV
Date: Fri, 13 Oct 2006 13:46:04 -0400	[thread overview]
Message-ID: <452FD0DC.5030904@waldoware.com> (raw)
In-Reply-To: <452FBCAA.4080000@redhat.com>

Bryn M. Reeves wrote:
[snip]
> 
> The problem here is that the LV is using striped allocation across 3 PVs:
[snip]
> 
> So, in order to extend it and maintain that allocation, you need to have
> 3 PVs with sufficient space to allocate three parallel stripes.
> 
> Cheers,
> 
> Bryn.
Thanks for the reply, Bryn.

OK, I'm confused.

The LVM Howto says "In LVM 2, striped LVs can be extended by concatenating 
another set of devices onto the end of the first set. So you can get into a 
situation where your LV is a 2 stripe set concatenated with a linear set 
concatenated with a 4 stripe set. Are you confused yet?"

I interpret the above to mean that I can concatenate the single drive after 
the existing stripped array.  Is that an incorrect interpretation?

Being as this LV stores backups, I don't really care too much that it is 
stripped--my goal is to have lots of disk space.  Is my only option trashing 
the existing LV and making it contiguous (non-stripped)?  Thanks!

Paul

  reply	other threads:[~2006-10-13 17:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-13 12:27 [linux-lvm] Unable to add new drive to LV Paul Waldo
2006-10-13 15:30 ` Klaus Strebel
2006-10-13 16:19   ` Bryn M. Reeves
2006-10-13 17:46     ` Paul Waldo [this message]
2006-10-13 18:37       ` Alasdair G Kergon
2006-10-13 19:48         ` Paul Waldo
2006-10-16  7:56     ` Klaus Strebel
2006-10-16 13:16       ` Paul Waldo

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=452FD0DC.5030904@waldoware.com \
    --to=pwaldo@waldoware.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.