linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Peter Smith <peter.smith@utsouthwestern.edu>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Problem with vgreduce on LVM1
Date: Tue, 29 Aug 2006 13:01:22 -0500	[thread overview]
Message-ID: <44F480F2.7070600@utsouthwestern.edu> (raw)
In-Reply-To: <EED09BB41EE72044BCEE8156094FCE8F0183821F@EVS4.its.caregroup.org>

Well, that is interesting. When I do a "pvdata", it does show an extent 
in use, one for each of the other LVs, but that is true for all the PVs 
for some reason. Any ideas on how to stop that? I've already tried a 
"pvmove" and it says the disk is empty.

[root@linux archive]# pvdata /dev/emcpowera
--- Physical volume ---
PV Name /dev/emcpowera
VG Name data
PV Size 785.10 GB [1646481408 secs] / NOT usable 1 GB [LVM: 127 KB]
PV# 1
PV Status available
Allocatable NO
Cur LV 4
PE Size (KByte) 1048576
Total PE 784
Free PE 784
Allocated PE 0
PV UUID JpYFFb-NUqC-trBf-oFm7-tbdF-65If-GZ56fw

--- Volume group ---
VG Name
VG Access read/write
VG Status NOT available/resizable
VG # 0
MAX LV 256
Cur LV 5
Open LV 0
MAX LV Size 2 TB
Max PV 256
Cur PV 8
Act PV 1
VG Size 12.21 TB
PE Size 1 GB
Total PE 12507
Alloc PE / Size 9078 / 886 GB
Free PE / Size 3429 / 3.35 TB
VG UUID 5Xw9D6-qqfu-0FTg-P9pD-40NH-wRgR-wN03ip

--- List of logical volumes ---

pvdata -- logical volume struct at offset 0 is empty
pvdata -- logical volume "/dev/data/data2" at offset 1
pvdata -- logical volume "/dev/data/data3" at offset 2
pvdata -- logical volume "/dev/data/data4" at offset 3
pvdata -- logical volume "/dev/data/data5" at offset 4
pvdata -- logical volume "/dev/data/data6" at offset 5
pvdata -- logical volume struct at offset 6 is empty
pvdata -- logical volume struct at offset 7 is empty
pvdata -- logical volume struct at offset 8 is empty
pvdata -- logical volume struct at offset 9 is empty
<SNIP>
pvdata -- logical volume struct at offset 254 is empty
pvdata -- logical volume struct at offset 255 is empty
--- List of physical volume UUIDs ---

001: JpYFFb-NUqC-trBf-oFm7-tbdF-65If-GZ56fw
002: ABNwWZ-h4la-KTcv-VukV-T8vV-PIEP-mm38cy
003: oyjw8S-B1gu-snoN-k54q-bCEy-daqn-BYdDmK
004: URW9Kt-ZbOn-Ov3h-ZiT5-i7aC-8Lpq-c0fp4l
005: y16lho-UgMJ-1lfJ-GNTi-VXWH-Pot1-iIsOc0
006: WEC9g3-fTKD-k8pV-Nnxq-Kwn3-EkNd-qV3lUE
007: TCxHIb-uvjC-6xap-bLaM-lVJU-N82x-XWd10g
008: fZkmf8-jaYW-1gZ6-WBqp-eNu2-s1xr-IBLQTe

Thanks,
Peter


mghofran@caregroup.harvard.edu wrote:

>You show lv=4 so don't you need to check if any of those lvols were
>using that particular disk, remove the lvol and then proceed?
>
>-----Original Message-----
>From: linux-lvm-bounces@redhat.com [mailto:linux-lvm-bounces@redhat.com]
>On Behalf Of Peter Smith
>Sent: Tuesday, August 29, 2006 12:21 PM
>To: linux-lvm@redhat.com
>Subject: [linux-lvm] Problem with vgreduce on LVM1
>
>I can't seem to remove two physical volumes.  I've removed the LVs on 
>them.  I've deactivated the PVs.  But I can not remove the PVs from the
>VG.
>
>Here's an example of what I'm seeing:
>
>[root@linux archive]# pvmove -v /dev/emcpowera
>pvmove -- checking name of source physical volume "/dev/emcpowera"
>pvmove -- locking logical volume manager
>pvmove -- reading data of source physical volume from "/dev/emcpowera"
>pvmove -- checking volume group existence
>pvmove -- reading data of volume group "data" from lvmtab
>pvmove -- checking volume group consistency of "data"
>pvmove -- searching for source physical volume "/dev/emcpowera" in 
>volume group "data"
>pvmove -- no logical volumes on empty source physical volume 
>"/dev/emcpowera"
>
>[root@linux archive]# vgreduce data /dev/emcpowera
>vgreduce -- ERROR: can't reduce volume group "data" by used physical 
>volume "/dev/emcpowera"
>
>[root@linux archive]# pvdisplay /dev/emcpowera
>--- Physical volume ---
>PV Name               /dev/emcpowera
>VG Name               data
>PV Size               785.10 GB [1646481408 secs] / NOT usable 1 GB 
>[LVM: 127 KB]
>PV#                   1
>PV Status             available
>Allocatable           NO
>Cur LV                4
>PE Size (KByte)       1048576
>Total PE              784
>Free PE               784
>Allocated PE          0
>PV UUID               JpYFFb-NUqC-trBf-oFm7-tbdF-65If-GZ56fw
>
>Does anyone have any idea why I can't complete a reduce?
>
>Thanks,
>Peter
>
>Note:
>Logical Volume Manager 1.0.8-13
>Heinz Mauelshagen, Red Hat  03/05/2005 (IOP 10)
>
>_______________________________________________
>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/
>
>
>
>_______________________________________________
>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/
>  
>

  reply	other threads:[~2006-08-29 18:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-29 16:41 [linux-lvm] Problem with vgreduce on LVM1 mghofran
2006-08-29 18:01 ` Peter Smith [this message]
2006-08-29 19:49   ` Peter Smith
2006-08-29 20:40     ` Peter Smith
2006-08-30  1:13       ` Peter Smith
2006-09-07 17:11         ` Peter Smith
2006-09-07 17:34           ` Peter Smith
  -- strict thread matches above, loose matches on Subject: below --
2006-08-29 16:21 Peter Smith

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=44F480F2.7070600@utsouthwestern.edu \
    --to=peter.smith@utsouthwestern.edu \
    --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).