linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: urgrue <urgrue@bulbous.org>
To: dermot@sciencephoto.co.uk
Cc: linux-admin@vger.kernel.org
Subject: Re: Expanding an LVM
Date: Tue, 19 Aug 2008 13:26:57 +0300	[thread overview]
Message-ID: <48AA9FF1.7020301@bulbous.org> (raw)
In-Reply-To: <48AA8E4C.4663.242117B3@dermot.sciencephoto.co.uk>

Dermot Paikkos wrote:
> Hi,
> 
> I think I may have made a error in the method I have used to create 
> more space on one of my servers.
> 
> Here's what I've done.
> 
> 1) Backed up the LVM volume (phew)
> 2) Added some disks to the storage array (HP MSA 20)
> 3) Used the HW Array configurator to do and on-line extend of the  
> Raid Array.
> 
> It was at this point I realised that I hadn't un-mounted the volume 
> in question. 
> 
> The other thing I am trying to figure out is, how I am going to 
> extend a Physical Volume? I think the procedure should have been to 
> add a completely new array and use pvcreate, vgextend, lvextend and  
> extended the filesystem (ext3).
> 
> Can anyone confirm if the procedure above is the correct? 

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.

  reply	other threads:[~2008-08-19 10:26 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 [this message]
2008-08-19 10:46   ` Dermot Paikkos
2008-08-19 11:51     ` urgrue

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=48AA9FF1.7020301@bulbous.org \
    --to=urgrue@bulbous.org \
    --cc=dermot@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).