All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rainer.Lay@informatik.uni-erlangen.de
To: linux-lvm@sistina.com
Cc: idsfa@visi.com
Subject: Re: [linux-lvm] cannot extend lv
Date: Sun Jan 19 03:15:01 2003	[thread overview]
Message-ID: <3E2A7AE4.8080801@informatik.uni-erlangen.de> (raw)

My idea was not to make a 4 stripe set with 4 PV, but a 2 stripe set:

stripe1: aaaaaaaaabbbbbb
stripe2: cccccccccdddddd

so if PV a and c are full, PV b and d are used.

I would create a new lv as you suggested, but drives a and c are two 
times bigger than b and d, so I thought about the above solution.

Rainer

>> I have a vg (data) with four drives /dev/sd[b-e]1
>> I created a 2 stripes lv (data1) with sd[bc]1
>                 ^^^^^^^
> 
> You cannot extend striped lvs onto new pvs. Even on the
> same physical hardware.  Once you have striped it, you are
> tied to the pvs used.
> 
> If you think about it, this makes sense, as otherwise you
> have some stripes containing more data than others.  In fact,
> as soon as the smallest pv is full, you will not be able to
> extend the lv, even if there is room in the other pvs.
> 
> If you want to have the filesystem striped over all the disks, you
> will need to create a new lv which is striped across them all,
> transfer the data to it, delete the old lv and then extend the
> new one.
> 
> Backups highly recommended.
> 
> Michael

             reply	other threads:[~2003-01-19  3:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-19  3:15 Rainer.Lay [this message]
2003-01-19 12:07 ` [linux-lvm] cannot extend lv idsfa
2003-01-19 13:31   ` Alasdair G Kergon
2003-01-19 15:00   ` Steven Lembark
  -- strict thread matches above, loose matches on Subject: below --
2003-01-18  4:36 Rainer.Lay
2003-01-18 10:57 ` idsfa

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=3E2A7AE4.8080801@informatik.uni-erlangen.de \
    --to=rainer.lay@informatik.uni-erlangen.de \
    --cc=idsfa@visi.com \
    --cc=linux-lvm@sistina.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.