All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Alexander <bob@ngi.it>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Please help with lvextend problems
Date: Mon, 05 Sep 2005 16:03:32 +0200	[thread overview]
Message-ID: <431C5034.6040604@ngi.it> (raw)

Trying to enlarge a LV after adding a new PV to the VG.

I get an horrible string of messages:

lvextend -L+400M /dev/vg1/lvusr
Extending logical volume lvusr to 3.09GB
Inconsistent length 66 71
PV segment pe_alloc_count mismatch: 1436 != 1520
PV segment VG free_count mismatch: 1570 != 1486
Internal error: PV segments corrupted in vg1

Am I toast ???

Here follows some additional data. Thank you
Bob Alexander

bob@t40:~$ uname -a
Linux t40 2.6.11.4T40237392G-RJA #1 Mon Mar 28 19:36:30 CEST 2005 i686 
GNU/Linux
t40:/home/bob# pvdisplay
   --- Physical volume ---
   PV Name               /dev/hda9
   VG Name               vg1
   PV Size               6.77 GB / not usable 0
   Allocatable           yes
   PE Size (KByte)       4096
   Total PE              1733
   Free PE               313
   Allocated PE          1420
   PV UUID               CSxEXj-LPQv-VAlv-gTxv-zLfa-2dZ4-MGN7T1

   --- Physical volume ---
   PV Name               /dev/hda8
   VG Name               vg1
   PV Size               4.97 GB / not usable 0
   Allocatable           yes
   PE Size (KByte)       4096
   Total PE              1273
   Free PE               1273
   Allocated PE          0
   PV UUID               FmDlz8-gBJ6-oH5X-Cg26-ZDdm-pTSh-obtzqG
t40:/home/bob# vgdisplay
   --- Volume group ---
   VG Name               vg1
   System ID
   Format                lvm2
   Metadata Areas        2
   Metadata Sequence No  19
   VG Access             read/write
   VG Status             resizable
   MAX LV                0
   Cur LV                5
   Open LV               5
   Max PV                0
   Cur PV                2
   Act PV                2
   VG Size               11.74 GB
   PE Size               4.00 MB
   Total PE              3006
   Alloc PE / Size       1420 / 5.55 GB
   Free  PE / Size       1586 / 6.20 GB
   VG UUID               sLbPHD-Fxe8-sMkh-pMk8-dvgK-2c8K-DKCEt8
t40:/home/bob# lvdisplay /dev/vg1/lvusr
   --- Logical volume ---
   LV Name                /dev/vg1/lvusr
   VG Name                vg1
   LV UUID                PeGQ6L-dqE6-KH7G-ErcU-pzAD-A6JM-ZEHM6x
   LV Write Access        read/write
   LV Status              available
   # open                 1
   LV Size                2.70 GB
   Current LE             690
   Segments               2
   Allocation             inherit
   Read ahead sectors     0
   Block device           254:1

             reply	other threads:[~2005-09-05 20:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-05 14:03 Bob Alexander [this message]
2005-09-05 20:15 ` [linux-lvm] Please help with lvextend problems Alasdair G Kergon
2005-09-05 14:22   ` Bob Alexander
2005-09-06 14:00     ` Bob Alexander

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=431C5034.6040604@ngi.it \
    --to=bob@ngi.it \
    --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 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.