From: idsfa@visi.com
To: linux-lvm@sistina.com
Cc: Rainer.Lay@informatik.uni-erlangen.de
Subject: Re: [linux-lvm] cannot extend lv
Date: Sun Jan 19 12:07:02 2003 [thread overview]
Message-ID: <20030119180753.GA15083@mitethe.eudyptes> (raw)
In-Reply-To: <3E2A7AE4.8080801@informatik.uni-erlangen.de>
[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]
On Sun, Jan 19, 2003 at 10:16:04AM +0000,
Rainer.Lay@informatik.uni-erlangen.de wrote:
> 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.
Striping doesn't work that way. It stripes across all pvs EVENLY
to improve access speeds (the whole reason to stripe). The only
way to do what you want would have been to use kernel RAID to combine
the physical devices into a single logical device before creating the
stripe set.
> 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.
I understand, I went through the same exercise two months ago. I
borrowed a disk from a friend, moved all of the data to it, and rebuilt
my whole VG setup. It was a major pain in the neck.
Michael
--
Think Locally, Act Globally:
"It's cold in here ... I'd better release a few million tons of CFCs!"
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-01-19 12:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-19 3:15 [linux-lvm] cannot extend lv Rainer.Lay
2003-01-19 12:07 ` idsfa [this message]
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=20030119180753.GA15083@mitethe.eudyptes \
--to=idsfa@visi.com \
--cc=Rainer.Lay@informatik.uni-erlangen.de \
--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.