From: Gavin McCullagh <gmccullagh@gmail.com>
To: Daniel Korstad <dan@korstad.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: FW: [slightly OT] expanding lvm volume group after growing raid5 array
Date: Thu, 19 Apr 2007 16:51:12 +0100 [thread overview]
Message-ID: <20070419155112.GL30056@gmail.com> (raw)
In-Reply-To: <1391903588.1176996087946.JavaMail.root@gateway.korstad.net>
Hi,
On Thu, 19 Apr 2007, Daniel Korstad wrote:
> I have used lv with my past raid sets and it is very nice, adds some
> flexibility.
>
> I have also done a RAID5 reshape that was in an lv. Unfortunately, at
> the time I had an older LVM version that did not support pvresize. So I
> was stuck with a larger RAID set and my lv would not take advantage of
> it.
Thanks. A guy in my local LUG pointed out that I had to do a pvresize
before I could do a vgresize.
I seem to be on my way now,
Gavin
prev parent reply other threads:[~2007-04-19 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-19 11:35 [slightly OT] expanding lvm volume group after growing raid5 array Gavin McCullagh
2007-04-19 15:21 ` FW: " Daniel Korstad
2007-04-19 15:51 ` Gavin McCullagh [this message]
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=20070419155112.GL30056@gmail.com \
--to=gmccullagh@gmail.com \
--cc=dan@korstad.net \
--cc=linux-raid@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).