From: David Grierson <david.grierson@lumison.net>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] LVM partition growth after Dell MegaRAID RAID array growth
Date: Fri, 04 Feb 2005 15:43:33 +0000 [thread overview]
Message-ID: <42039825.2040408@lumison.net> (raw)
Hi,
I'm in the process of installing (so fortunately can reformat, rinse,
repeat as necessary) a new Dell PowerVault attached to a PowerEdge
running RHEL3.
I'm looking to have the facility to be able to grow the RAID arrays at a
later date. The Dell PERC 4/DC card installed supports growing the RAID
array, however since I created the physical volume to utilise the whole
disk it hasn't seen the growth in the PV:
> [root@nbg01-filer-01 root]# pvdisplay /dev/sdb
> --- Physical volume ---
> PV Name /dev/sdb
> VG Name splitbus0
> PV Size 546.48 GB [1146060800 secs] / NOT usable 32.25 MB [LVM: 196 KB]
> PV# 1
> PV Status NOT available
> Allocatable yes (but full)
> Cur LV 1
> PE Size (KByte) 32768
> Total PE 17486
> Free PE 0
> Allocated PE 17486
> PV UUID duXmrI-c1d0-pPew-VNL4-ce6N-5h14-6swMqK
However lvmdiskscan recognises that the disk has grown in capacity:
> [root@nbg01-filer-01 root]# lvmdiskscan
> lvmdiskscan -- reading all disks / partitions (this may take a while...)
> ...
> lvmdiskscan -- /dev/sdb [ 683.11 GB] USED LVM whole disk
> ...
Looking at the lists I realise that extending the physical volumes isn't
supported yet.
So, to ask my question (about time too I hear you say), what advice
would you give me in order to achieve expandability of the RAID array at
a later date when we have filled existing capacity?
Should I partition /dev/sdb before I create the physical volume and then
partition any new space which is added and then add those partitions to
the volume group? Or is there some more clever way to do it?
Cheers,
Dg.
--
David Grierson
Lumison
t: 0845 1199 900
d: +44 131 514 4053
--
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the sender. Any
offers or quotation of service are subject to formal specification.
Errors and omissions excepted. Please note that any views or opinions
presented in this email are solely those of the author and do not
necessarily represent those of Lumison, nplusone or lightershade ltd.
Finally, the recipient should check this email and any attachments for the
presence of viruses. Lumison, nplusone and lightershade ltd accepts no
liability for any damage caused by any virus transmitted by this email.
--
--
Virus scanned by Lumison.
reply other threads:[~2005-02-04 15:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=42039825.2040408@lumison.net \
--to=david.grierson@lumison.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