A server, to which I only have remote access has a raid with lvm and reiserfs partitions on it. I will limit the information to the /home partition in the following, other partitions have the same problem. All information is taken from a rescue system (PXE boot), which is offered by the provider. Booting into the rescue system, I can get the following information:

root@rescue ~ # vgdisplay
  --- Volume group ---
  VG Name               systemlvm
  System ID
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  19
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                4
  Open LV               0
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               144.75 GB
  PE Size               128.00 MB
  Total PE              1158
  Alloc PE / Size       952 / 119.00 GB
  Free  PE / Size       206 / 25.75 GB
  VG UUID               rL8Oq2-dA7o-eRYe-u1or-JA7U-fnb1-kjOyvr


root@rescue ~ # lvdisplay
  --- Logical volume ---
  LV Name                /dev/systemlvm/home
  VG Name                systemlvm
  LV UUID                YXrfdg-5OSY-DVkN-eiQe-Qksg-CI84-9Z2hx8
  LV Write Access        read/write
  LV Status              available
  # open                 0
  LV Size                17.00 GB
  Current LE             136
  Segments               4
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:0
[... and other lvs here ...]


root@rescue ~ # mount /dev/systemlvm/home /mnt/
root@rescue ~ # df -Th /mnt/
Filesystem    Type    Size  Used Avail Use% Mounted on
/dev/mapper/systemlvm-home
          reiserfs     17G  8.2G  8.9G  48% /mnt


root@rescue ~ # lvm version
  LVM version:     2.02.39 (2008-06-27)
  Library version: 1.02.27 (2008-06-25)
  Driver version:  4.14.0

If I now boot into the actual system, not the rescue system, I get:

kermit:~# vgdisplay
  --- Volume group ---
  VG Name               systemlvm
  System ID
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  19
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                4
  Open LV               4
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               144,75 GB
  PE Size               128,00 MB
  Total PE              1158
  Alloc PE / Size       952 / 119,00 GB
  Free  PE / Size       206 / 25,75 GB
  VG UUID               rL8Oq2-dA7o-eRYe-u1or-JA7U-fnb1-kjOyvr


kermit:~# lvdisplay
  --- Logical volume ---
  LV Name                /dev/systemlvm/home
  VG Name                systemlvm
  LV UUID                YXrfdg-5OSY-DVkN-eiQe-Qksg-CI84-9Z2hx8
  LV Write Access        read/write
  LV Status              available
  # open                 2
  LV Size                17,00 GB
  Current LE             136
  Segments               4
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:0
[...]

Now for the not-so-funny part:

kermit:~# df -Th /home/
Dateisystem   Typ    Größe Benut  Verf Ben% Eingehängt auf
/dev/mapper/systemlvm-home
          reiserfs     14G  649M   14G   5% /home


kermit:~# lvm version
  LVM version:     2.02.39 (2008-06-27)
  Library version: 1.02.27 (2008-06-25)
  Driver version:  4.13.0

What is wrong here? I am not sure if the problem really lies within LVM, but it is my best guess so far ...

The same problem appears on the other lvm volumes as well.

Thanks for ANY hint!

link|improve this question

1  
It'll also murder your wife. – Tom O'Connor Nov 26 '10 at 11:25
feedback

1 Answer

up vote 0 down vote accepted

I didn't find a solution but with an update to the whole system the problem disappeared. Closing.

link|improve this answer
feedback

Your Answer

 
or
required, but never shown

Not the answer you're looking for? Browse other questions tagged or ask your own question.