From: Andreas Dilger <adilger@turbolabs.com>
To: John Moser <jmoser@erc.wisc.edu>
Cc: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Partition resizing and whatnot
Date: Wed Feb 20 17:31:02 2002 [thread overview]
Message-ID: <20020220163107.H1506@lynx.adilger.int> (raw)
In-Reply-To: <CBEHLLOPCKAOIAOINGKAMEHOCAAA.jmoser@erc.wisc.edu>; from jmoser@erc.wisc.edu on Wed, Feb 20, 2002 at 03:40:35PM -0600
On Feb 20, 2002 15:40 -0600, John Moser wrote:
> So, after installation the ATA update patches that people recommended, I now
> have a linux system that recognizes the full 160 gigabytes of disk space on
> my disks. However, I'm not entirely sure as to how I should go about
> resizing my filesystem. I'm already well aquanted with adding disks to
> existing filesystems and growing them. However, what are the recommended
> steps for taking existing disk partitions, resizing them to fill the disks
> they reside on, and then resizing the LVM/e2fs filesystems that use those
> disks?
With the current LVM setup, you are probably just as well off to create a
new partition on the remaining space, make it a PV, and then use the PEs
as you see fit. Anything else means binary editing of PV and VG structs
at this point, so you probably don't want to do it...
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2002-02-20 17:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-23 19:24 [linux-lvm] Automatically GROW an LV to max size Tracy R Reed
2002-01-23 19:31 ` Steve Wray
2002-01-23 20:15 ` Markus Dobel
2002-02-04 12:46 ` [linux-lvm] I/O Error removing a file John Moser
2002-02-05 3:59 ` Heinz J . Mauelshagen
2002-02-05 10:38 ` John Moser
2002-02-20 15:37 ` [linux-lvm] Partition resizing and whatnot John Moser
2002-02-20 17:31 ` Andreas Dilger [this message]
2002-02-21 2:57 ` William Blunn
2002-01-23 20:26 ` [linux-lvm] Automatically GROW an LV to max size Petro
2002-01-24 6:36 ` Heinz J . Mauelshagen
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=20020220163107.H1506@lynx.adilger.int \
--to=adilger@turbolabs.com \
--cc=jmoser@erc.wisc.edu \
--cc=linux-lvm@sistina.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.