linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Heinz Mauelshagen <mauelshagen@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] can t resize my lvm
Date: Tue, 22 Nov 2005 10:58:20 +0100	[thread overview]
Message-ID: <20051122095820.GE30556@redhat.com> (raw)
In-Reply-To: <200511212322.52680.Matthias.Meyer@gmx.li>


Matthias,

you don't need to deactivate your VG in order to grow it.

That's the whole point behind LVM: be able to adjust your changing
storage requirements online.

Do "vgchange -ay", "vgextend LVM2 /dev/hdc1" and you'll have your
VG online with extended capacity to grow your LV and FS in another step.

Regards,
Heinz    -- The LVM Guy --


On Mon, Nov 21, 2005 at 11:22:52PM +0100, Matthias Meyer wrote:
> And now I do:
> vdr:~# vgchange -an LVM2
> vgchange -- volume group "LVM2" successfully deactivated
> 
> vdr:~# pvcreate -vff /dev/hdc1
> pvcreate -- locking logical volume manager
> pvcreate -- checking physical volume name "/dev/hdc1"
> pvcreate -- getting physical volume size
> pvcreate -- checking maximum physical volume size
> pvcreate -- checking partition type
> pvcreate -- checking volume group name
> pvcreate -- really INITIALIZE physical volume "/dev/hdc1" of volume group 
> "LVM2" [y/n]? y
> pvcreate -- WARNING: forcing physical volume creation on "/dev/hdc1" of 
> volume group "LVM2"
> pvcreate -- removing lvmtab entry
> pvcreate -- creating new physical volume
> pvcreate -- setting up physical volume for /dev/hdc1 with 195318207 sectors
> pvcreate -- writing physical volume data to disk "/dev/hdc1"
> pvcreate -- physical volume "/dev/hdc1" successfully created
> pvcreate -- unlocking logical volume manager
> 
> and hove no more access to the volume group.
> But it exists:
> vdr:~# dir /dev/LVM2/Media
> /dev/LVM2/Media
> 
> -- 
> Don't Panic
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Red Hat GmbH
Consulting Development Engineer                   Am Sonnenhang 11
Cluster and Storage Development                   56242 Marienrachdorf
                                                  Germany
Mauelshagen@RedHat.com                            +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2005-11-22  9:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-21 18:34 [linux-lvm] can't resize my lvm Matthias Meyer
2005-11-21 22:22 ` [linux-lvm] can t " Matthias Meyer
2005-11-22  9:58   ` Heinz Mauelshagen [this message]
2005-11-22 22:26     ` Matthias Meyer
2005-11-22 23:02       ` Heinz Mauelshagen
2005-11-23  1:10         ` Matthias Meyer
2005-11-23 22:36           ` Matthias Meyer
2005-11-25 20:21 ` Matthias Meyer
2005-11-27 13:07   ` Matthias Meyer

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=20051122095820.GE30556@redhat.com \
    --to=mauelshagen@redhat.com \
    --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).