From: Ben <bench@silentmedia.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Expanding volume groups to fill a growing disk
Date: Thu, 2 Feb 2006 17:10:34 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0602021709110.1276@localhost.localdomain> (raw)
In-Reply-To: <20060203003308.GA20335@loon.fatav.hu>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1321 bytes --]
Ah, thanks, that should be good enough. I plan to upgrade to FC5T3 as soon as it
comes out for the x86_64 Xen support it will hopefully provide. And also, it
seems, for a working packaged version of pvresize. :)
On Fri, 3 Feb 2006, Szabo Akos wrote:
> On Thu, Feb 02, 2006 at 03:40:57PM -0800, Ben wrote:
>> What version do I need?
>
> At least I don;t no, but I have tha bleow, BTW I never use it!
>
> /I use fedore FC5T.
> device-mapper-1.02.02-3
> lvm2-2.02.01-1.1/
>
> pvresize --help
> pvresize: Resize physical volume(s)
>
> pvresize
> [-d|--debug]
> [-h|-?|--help]
> [--setphysicalvolumesize PhysicalVolumeSize[kKmMgGtT]
> [-t|--test]
> [-v|--verbose]
> [--version]
> PhysicalVolume [PhysicalVolume...]
>
> pvresize --version
> LVM version: 2.02.01 (2005-11-23)
> Library version: 1.02.02 (2005-12-02)
> Driver version: 4.5.0
>
>
> --
> Ciao:
> Fonya
>
> Ami�ta NT-t install�ltam a porsz�v�mra, semmi sz�v�s nincs vele.
> PGP key ID F86614E5, GPG key ID 83AD9365
>
> _______________________________________________
> 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/
>
prev parent reply other threads:[~2006-02-03 1:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 23:06 [linux-lvm] Expanding volume groups to fill a growing disk Ben
2006-02-02 23:25 ` Alasdair G Kergon
2006-02-02 23:40 ` Ben
2006-02-03 0:33 ` Szabo Akos
2006-02-03 1:10 ` Ben [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=Pine.LNX.4.64.0602021709110.1276@localhost.localdomain \
--to=bench@silentmedia.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).