From: Antoine <lists@chwing.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] free space and no free PE
Date: Fri, 26 Aug 2005 14:31:33 +0200 [thread overview]
Message-ID: <430F0BA5.4010103@chwing.com> (raw)
In-Reply-To: <430F0279.2090901@gmx.net>
you're right, I wrongly assumed that PE = space
thanks
Klaus Strebel wrote:
> Antoine schrieb:
>
>> Hi
>>
>> I'm trying to remove a PV from a VG but I'm unable to perform the
>> pvmove because the free PE doesn't match the free space on the VG..
>> at all.
>
> Who do you come to this conlusion??? vgdisplay shows 677 free PE's and
> the only free PE in your PV is 677 on /dev/sdb1. So what???
>
> The free PEs have nothing to do with the df output. You have to shrink
> your filesystem (what might be not possible, not all fs's support
> this) to get as much free PE's as your PV has.
>
> Ex.: You wanna remove /dev/sdb1, shrink your filesystem to (size -
> 16.87 GB, or better less ;-) ), shrink your LV the same way, pvmove
> the extends on the PV, remove the PV from the VG.
>
> Ciao
> Klaus
>
>>
>> check output below, anyone has a clue why ? and how to correct this ?
>>
>> pitch:~# df -h /mnt/test
>> Filesystem Size Used Avail Use% Mounted on
>> /dev/mapper/vg1-test 64G 16G 45G 27% /mnt/test
>> pitch:~#
>> pitch:~#
>> pitch:~# vgdisplay vg1
>> --- Volume group ---
>> VG Name vg1
>> System ID
>> Format lvm2
>> Metadata Areas 3
>> Metadata Sequence No 6
>> VG Access read/write
>> VG Status resizable
>> MAX LV 0
>> Cur LV 1
>> Open LV 1
>> Max PV 0
>> Cur PV 3
>> Act PV 3
>> VG Size 67.64 GB
>> PE Size 4.00 MB
>> Total PE 17317
>> Alloc PE / Size 16640 / 65.00 GB
>> Free PE / Size 677 / 2.64 GB
>> VG UUID V9T0P5-PCML-z92w-GZot-Utlt-7GFF-z83i99
>> pitch:~# pvmove --version
>> LVM version: 2.01.04 (2005-02-09)
>> Library version: 1.01.00-ioctl (2005-01-17)
>> Driver version: 4.1.1
>>
>> pitch:~# pvdisplay
>> --- Physical volume ---
>> PV Name /dev/sda1
>> VG Name vg1
>> PV Size 16.87 GB / not usable 0
>> Allocatable yes (but full)
>> PE Size (KByte) 4096
>> Total PE 4318
>> Free PE 0
>> Allocated PE 4318
>> PV UUID 64vFFO-7kRV-oAYa-6dxH-vLod-XClo-wX3h54
>>
>> --- Physical volume ---
>> PV Name /dev/sdb1
>> VG Name vg1
>> PV Size 16.87 GB / not usable 0
>> Allocatable yes
>> PE Size (KByte) 4096
>> Total PE 4318
>> Free PE 677
>> Allocated PE 3641
>> PV UUID tAGCYo-8wGA-Y1Nr-8d0T-Wn0d-k9PW-Nf5bYj
>>
>> --- Physical volume ---
>> PV Name /dev/sdc1
>> VG Name vg1
>> PV Size 33.91 GB / not usable 0
>> Allocatable yes (but full)
>> PE Size (KByte) 4096
>> Total PE 8681
>> Free PE 0
>> Allocated PE 8681
>> PV UUID ZYn0Lr-rVyB-9geT-pbfN-VQCg-vhcO-kHCYin
>>
>> pitch:~# lvdisplay
>> --- Logical volume ---
>> LV Name /dev/vg1/test
>> VG Name vg1
>> LV UUID Bge5z0-EWMD-vnQs-a08Y-beJR-uyFO-dxg0sj
>> LV Write Access read/write
>> LV Status available
>> # open 1
>> LV Size 65.00 GB
>> Current LE 16640
>> Segments 5
>> Allocation contiguous
>> Read ahead sectors 0
>> Block device 254:1
>
>
>
prev parent reply other threads:[~2005-08-26 12:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-26 11:00 [linux-lvm] free space and no free PE Antoine
2005-08-26 11:52 ` Klaus Strebel
2005-08-26 12:31 ` Antoine [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=430F0BA5.4010103@chwing.com \
--to=lists@chwing.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).