From: urgrue <urgrue@bulbous.org>
To: Dermot Paikkos <Dermot.Paikkos@sciencephoto.co.uk>
Cc: linux-admin@vger.kernel.org
Subject: Re: Expanding an LVM
Date: Tue, 19 Aug 2008 14:51:30 +0300 [thread overview]
Message-ID: <48AAB3C2.8020601@bulbous.org> (raw)
In-Reply-To: <L07B328FD0A9D4bbfAFDAEDDD109FD3AB.1219142775.earth.sciencephoto.co.uk@MHS>
Dermot Paikkos wrote:
> Hi,
>
>> -----Original Message-----
>> From: urgrue [mailto:urgrue@bulbous.org]
>> Sent: 19 August 2008 11:27
>>
>> Correct. You dont expand the PV, you make a new partition with fdisk
> in
>> the new space and then create a pv on it, add it to the vg with
>> vgextend, and the lvextend and then ext2online/resize2fs/whatever to
>> expand the fs.
>
>>> Right now I am considering deleting the RAID container completely
> and
>>> re-creating and restoring rather than waste any more time but before
>>> I do I'd like to hear it if sounds like the procedure is bound to
>>> fail.
>>>
>>> At the moment I think the best I can hope for is that the volume
> will
>>> be fine but the extra disk-space will never be seen?
>>>
>> if you dont see the new space in fdisk, you might have to reboot, or
> do
>> echo "- - -" > /sys/class/scsi_host/hostXXX/scan.
>
> Do you mean the new space on the expanded RAID logical drive or a
> completely new RAID container?
>
I mean the new space on the existing RAID drive. If you used the RAID
tools to expand the existing array onto the same logical drive as
before, then from linux's point of view the underlying disk just "got
bigger", and it may require a reboot or the scsi scan i mentioned to get
linux to notice.
If you made a new logical drive, then it will appear as a new disk (in
linux). This too will require either a reboot or the scsi scan.
Either way, you then have to use fdisk to make a partition on the new
space and then pvcreate etc.
prev parent reply other threads:[~2008-08-19 11:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 8:11 Expanding an LVM Dermot Paikkos
2008-08-19 10:26 ` urgrue
2008-08-19 10:46 ` Dermot Paikkos
2008-08-19 11:51 ` urgrue [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=48AAB3C2.8020601@bulbous.org \
--to=urgrue@bulbous.org \
--cc=Dermot.Paikkos@sciencephoto.co.uk \
--cc=linux-admin@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).