From: Jan Niehusmann <list039@gondor.com>
To: Jan Niehusmann <list039@gondor.com>, linux-lvm@sistina.com
Subject: Re: [linux-lvm] *** ANNOUNCEMENT *** LVM 0.9.1 beta1 available at www.sistina.com
Date: Sun, 14 Jan 2001 15:17:56 +0100 [thread overview]
Message-ID: <20010114151756.A1050@gondor.com> (raw)
In-Reply-To: <20010114142913.A4966@gondor.com>; from list039@gondor.com on Sun, Jan 14, 2001 at 02:29:13PM +0100
Another thing with 0.9.1 - or to be exact, 0.9.1 userlevel tools
with the pv order patch, and a 2.4.1-pre3 kernel
(didn't test with other versions):
I issued the following commands:
pvmove /dev/sda2
vgreduce vg1 /dev/sda2
vgscan
(You guess it - I just removed an old scsi drive from my VG)
Afterwards I wanted to see if everything was OK and did a vgdisplay -v:
--- Volume group ---
VG Name vg1
VG Access read/write
VG Status available/resizable
VG # 0
MAX LV 256
Cur LV 23
Open LV 20
MAX LV Size 1023.97 GB
Max PV 256
Cur PV 1
Act PV 1
VG Size 72.95 GB
PE Size 16 MB
Total PE 4669
Alloc PE / Size 3217 / 50.27 GB
Free PE / Size 1452 / 22.69 GB
VG UUID 5HozPs-vN3u-eT3i-LNQp-eAE0-8HIS-KPy1O7
--- Logical volume ---
[...]
--- Physical volumes ---
PV Name (#) /dev/hda5 (1)
PV Status available / allocatable
Total PE / Free PE 414 / 0
Uh, what? Only one PV? Where is the other one, /dev/hdc4 with 4447 PEs?
But the system still works well, and vgdisplay -D shows all the PVs.
So I just rebooted and now everything is fine again.
Any idea what may have caused that behaviour?
Jan
prev parent reply other threads:[~2001-01-14 14:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-13 1:15 [linux-lvm] *** ANNOUNCEMENT *** LVM 0.9.1 beta1 available at www.sistina.com Heinz J. Mauelshagen
2001-01-13 16:04 ` Jan Niehusmann
2001-01-13 18:08 ` Holger Grothe
2001-01-13 18:30 ` Holger Grothe
2001-01-13 20:59 ` William L. Jones
2001-01-13 22:35 ` Rob Fugina
2001-01-13 23:26 ` Steven Lembark
2001-01-14 13:29 ` Jan Niehusmann
2001-01-14 14:17 ` Jan Niehusmann [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=20010114151756.A1050@gondor.com \
--to=list039@gondor.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox