From: Nils Juergens <nils@muon.de>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Best practice for lvm on raid-5
Date: Mon Feb 2 11:22:02 2004 [thread overview]
Message-ID: <20040202162025.GA27150@muon.de> (raw)
In-Reply-To: <20040202153506.GN5191@deepthought.hausboot.org>
On Mon, 02.02.04, Jens Hoffrichter <joho@hausboot.org> 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.
If you add another array (raid1 or raid5) as /dev/md1, you can vgextend your
VG.
cheers,
Nils
--
Nils Juergens | nils@muon.de | icq 7090774
Having problems sending big files over the net?
Try out Efisto (http://efisto.rnbhq.org).
next prev parent reply other threads:[~2004-02-02 11:22 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 [this message]
2004-02-02 13:30 ` Jens Hoffrichter
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=20040202162025.GA27150@muon.de \
--to=nils@muon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox