From: "Greg Hartzog" <glhartzog@comcast.net>
To: 'LVM general discussion and development' <linux-lvm@redhat.com>
Subject: RE: [linux-lvm] LVM2 on hardware RAID
Date: Fri, 11 Aug 2006 15:26:44 -0400 [thread overview]
Message-ID: <000e01c6bd7c$14ef4fa0$640a0a0a@laptopoptimus> (raw)
In-Reply-To: <73A8ABE78537AE4E9DB1D70863B8275F0330CD7C@exchange2k.lims.com>
[-- Attachment #1: Type: text/plain, Size: 2248 bytes --]
I believe you will do the following:
"pvresive /dev/sdb"
That will make the volume group now be 600GB.
Then use "lvextend" to enlarge the logical volumes, and whatever the proper
tool is to extend the EXT3 filesystem.
Best to have the logical volumes & volume group offline ("vgchange -a n")
before starting resizing.
Just my $0.02.
_____
From: linux-lvm-bounces@redhat.com [mailto:linux-lvm-bounces@redhat.com] On
Behalf Of Musil, William
Sent: Friday, August 11, 2006 12:49 PM
To: linux-lvm@redhat.com
Subject: [linux-lvm] LVM2 on hardware RAID
Hello all.
I have an issue, that I am not sure how to address.
How can I resize the physical volume if I change the geometry of the disk
(non-destructive resize of RAID volume at the hardware level)
I can see that the OS has picked up the new size of the disk and I would
like to resize the existing pv. I don't know how.
I started with a hardware raid 5 (400GB), linux automatically recognizes
disk as /dev/sdb
a simplistic representation of the setup is as follows
pvcreate /dev/sdb
vgcreate VolGroup10 /dev/sdb
lvcreate -n LogVol10 VolGroup10
mkfs.ext3 /dev/mapper/VolGroup10-LogVol10
I have added a disk and expand the array to 600GB I can still see every
thing but I don't know how to extend the PV.
filesystems OK
logical volumes OK
volume groups OK
linux sees /dev/sdb as 600GB
pvs shows pv /dev/sdb is 400GB. I wish to, non-destructively, reinitialize
/dev/sdb so that pvs shows 600GB. how?
William T. Musil
Manager, Technical Services
LabVantage Solutions, Inc.
1160 US Highway 22 East, Bridgewater, NJ 08807
p| 908.333.0111
f | 908.707.1179
e| wmusil@labvantage.com
i | www.labvantage.com
The information in this e-mail is confidential and may contain legally
privileged information. It is intended solely for the person or entity to
which it is addressed. Access to this e-mail by anyone else is unauthorized.
If you are not the intended recipient, any disclosure, copying,
distribution, action taken, or action omitted to be taken in reliance on it,
is prohibited and may be unlawful. If you received this e-mail in error,
please contact the sender and delete the material from any computer.
<<Musil, William.vcf>>
[-- Attachment #2: Type: text/html, Size: 11137 bytes --]
next prev parent reply other threads:[~2006-08-11 19:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-11 16:48 [linux-lvm] LVM2 on hardware RAID Musil, William
2006-08-11 17:24 ` paddy
2006-08-11 19:26 ` Greg Hartzog [this message]
2006-08-14 20:55 ` paddy
-- strict thread matches above, loose matches on Subject: below --
2006-08-11 19:37 Musil, William
2006-08-14 22:36 ` paddy
2006-08-14 22:57 ` Zak Kipling
2006-08-14 23:46 ` paddy
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='000e01c6bd7c$14ef4fa0$640a0a0a@laptopoptimus' \
--to=glhartzog@comcast.net \
--cc=linux-lvm@redhat.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;
as well as URLs for NNTP newsgroup(s).