linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Roger Lucas" <roger@planbit.co.uk>
To: 'LVM general discussion and development' <linux-lvm@redhat.com>
Subject: [linux-lvm] Situation with PVRESIZE command
Date: Tue, 21 Feb 2006 18:00:54 -0000	[thread overview]
Message-ID: <20060221180029.B14FF12ECC@bluewhale.planbit.co.uk> (raw)
In-Reply-To: <20060220221114.GB16484@percy.comedia.it>

Hi,

I am running LVM on top of a large RAID controller with a 16-drive
capability (of which just 4 disks are currently active).  The RAID array
appears as a single SCSI disk, "/dev/sda".  A quick summary of the LVM
information is below.

tiger:~# lvm version
  LVM version:     2.01.04 (2005-02-09)
  Library version: 1.01.00-ioctl (2005-01-17)
  Driver version:  4.4.0
tiger:~# pvs
  PV         VG      Fmt  Attr PSize   PFree
  /dev/sda   storage lvm2 a-   745.05G 39.05G
tiger:~# vgs
  VG      #PV #LV #SN Attr  VSize   VFree
  storage   1   3   0 wz--n 745.05G 39.05G
tiger:~# lvs
  LV   VG      Attr   LSize Origin Snap%  Move Copy%
  home storage -wi-ao 2.00G
  root storage -wi-ao 2.00G
  var  storage -wi-ao 2.00G
  main storage -wi-ao 700.0G
tiger:~# mount
/dev/mapper/storage-root on / type reiserfs (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw)
/dev/hda1 on /boot type ext3 (rw,noatime)
/dev/mapper/storage-home on /home type reiserfs (rw)
/dev/mapper/storage-var on /var type reiserfs (rw)
/dev/mapper/storage-main on /main type reiserfs (rw)
usbfs on /proc/bus/usb type usbfs (rw)
tmpfs on /dev type tmpfs (rw,size=10M,mode=0755)
tiger:~#

I now need to increase my RAID capacity.  I can increase the physical RAID
capacity by adding another disk to the controller and getting it to re-build
the array in the background, thus increasing the size of "/dev/sda", but I
am not clear as to how I can increase the PV size in LVM.  

I have seen some references to a "pvresize" command, but it isn't in the
latest 2.01.15 stable release (although it does appear in the 2.02.02
development release).

Hence, my questions are:

- Is it possible to re-size a PV whilst the system is online using the
2.01.15 tools?

- Is it possible to re-size a PV whilst the system is online using the
2.02.02 tools?

- How "stable" are the 2.02.02 tools, and are there any specific bugs in
them that may cause problems during typical usage.

Thanks,

Roger

  parent reply	other threads:[~2006-02-21 18:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-20 19:28 [linux-lvm] Using LVM to snapshot Oracle Mitchell Christensen
2006-02-20 22:05 ` Luca Berra
2006-02-20 22:11   ` Luca Berra
2006-02-21 10:21     ` Klaus Strebel
2006-02-21 18:00     ` Roger Lucas [this message]
2006-02-28 13:32       ` [linux-lvm] Situation with PVRESIZE command Roger Lucas
2006-02-28 13:53       ` Patrick Caulfield
2006-02-28 15:51         ` Roger Lucas
2006-02-28 16:04           ` Patrick Caulfield
2006-02-28 16:07             ` Roger Lucas

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=20060221180029.B14FF12ECC@bluewhale.planbit.co.uk \
    --to=roger@planbit.co.uk \
    --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).