From: Jens Hoffrichter <joho@hausboot.org>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Best practice for lvm on raid-5
Date: Mon Feb 2 13:30:02 2004 [thread overview]
Message-ID: <20040202182846.GO5191@deepthought.hausboot.org> (raw)
In-Reply-To: <20040202162025.GA27150@muon.de>
On Mon, Feb 02, 2004 at 05:20:25PM +0100, Nils Juergens wrote:
> > Currently I have /dev/md0 as my only physical volume, but this will lead
> > to problems if I am going to expand the raid 5 by adding another 80 GB
> > harddrive to (as pvresize is not implemented again yet, as I understand).
>
> Unless I am mistaken, it is not even possible to expand /dev/md0 by adding
> another drive in the first place. And because linux software raid has
> no way of knowing which blocks are in use and which are not, i do not see
> how this could ever be possible.
Yes, it should be possible using raidreconf. I have not testet it yet, but
at least the manpage states it. Converting a raid 0 to a raid 5 of same size
worked without problem.
> If you add another array (raid1 or raid5) as /dev/md1, you can vgextend your
> VG.
Yes, I'm aware of this, but for this I have to add another 3 disk to the
system, and I want to avoid this.
CU all,
Jens
--
GPG: 1024D/CF884D50 F2E8 F7FC F823 6464 4E9D EFAB 6EE9 8B9C CF88 4D50
------------------------------------------------------------------------
Jens Hoffrichter / joho@hausboot.org / Joho@IRC / Fon: +43-650-5376989
A dream is a wish your heart makes.
(Seen on a parade in Walt Disney World)
next prev parent reply other threads:[~2004-02-02 13:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 10:36 [linux-lvm] Best practice for lvm on raid-5 Jens Hoffrichter
2004-02-02 11:22 ` Nils Juergens
2004-02-02 13:30 ` Jens Hoffrichter [this message]
2004-02-02 14:37 ` Chris Cox
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=20040202182846.GO5191@deepthought.hausboot.org \
--to=joho@hausboot.org \
--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.