You are not logged in.

Pages: 1

#1 2011-02-05 13:35:23

vendion
Member
From: Tennessee, USA
Registered: 2010-03-10
Posts: 204
Website

LVM2 incorrectly reporting one of my drives are full

I have three drives in a LVM group and the pvdisplay is saying that one of my drives is full but when I look at df my system usage only says I'm using only a couple of gigs.  The following is the output of both pvdisplay, lvdisplay, and df:

  --- Physical volume ---
  PV Name               /dev/sda3
  VG Name               system
  PV Size               84.20 GiB / not usable 4.02 MiB
  Allocatable           yes 
  PE Size               4.00 MiB
  Total PE              21553
  Free PE               21553
  Allocated PE          0
  PV UUID               1Rd2rD-WXPd-4V43-Rn8a-3iq9-Gzr9-KnGBVc
   
  --- Physical volume ---
  PV Name               /dev/sdb1
  VG Name               system
  PV Size               232.88 GiB / not usable 673.00 KiB
  Allocatable           yes (but full)
  PE Size               4.00 MiB
  Total PE              59618
  Free PE               0
  Allocated PE          59618
  PV UUID               1SKHYW-q8GQ-mafu-DhHd-Xprk-wxsr-NzPPQ7
   
  --- Physical volume ---
  PV Name               /dev/sdc1
  VG Name               system
  PV Size               232.88 GiB / not usable 673.00 KiB
  Allocatable           yes 
  PE Size               4.00 MiB
  Total PE              59618
  Free PE               36248
  Allocated PE          23370
  PV UUID               5aXwSX-CfqT-dGol-GEyl-2RTJ-WFvP-fycHZX
 --- Logical volume ---
  LV Name                /dev/system/root
  VG Name                system
  LV UUID                QKjbN4-3xO3-bAJC-xgzL-5tdz-92lw-i7jp5w
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                320.00 GiB
  Current LE             81920
  Segments               2
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:0
   
  --- Logical volume ---
  LV Name                /dev/system/swap
  VG Name                system
  LV UUID                5yeEwa-OcX5-tRlJ-6jXQ-ubI5-XMEj-I6Mjul
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                4.00 GiB
  Current LE             1024
  Segments               1
  Allocation             contiguous
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:1
   
   
  --- Logical volume ---
  LV Name                /dev/system/home
  VG Name                system
  LV UUID                t41cTt-jMVO-QaHX-keSq-1u96-x1dU-MffUS9
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                176.00 MiB
  Current LE             44
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:2
Filesystem            Size  Used Avail Use% Mounted on                          
udev                   10M  128K  9.9M   2% /dev                                
/dev/dm-0             320G  1.9G  319G   1% /                                   
shm                  1004M     0 1004M   0% /dev/shm                            
/dev/mapper/system-home                                                         
                      175M  2.8M  173M   2% /home                               
/dev/sda2             376G  1.5G  355G   1% /backups                            
/dev/sda1              92M   17M   70M  20% /boot

Another question I have is why does one of my logical volumes show as /dev/dm-0 instead of /dev/mapper/system-root?

Offline

#2 2011-02-05 21:56:03

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,911

Re: LVM2 incorrectly reporting one of my drives are full

Allocatable           yes (but full)

from pvdisplay means that you have assigned the space on that PV to a logical volume.

DF doesn't show LVM physical volumes, it only displays data about filesystems on logical volumes.


sda3 and sdc1 are physical volumes, but are not assigned to  a LV, so that space is doing nothing atm.

your other question about dm-0 i don't have an answer fro.

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#3 2011-02-05 22:39:29

vendion
Member
From: Tennessee, USA
Registered: 2010-03-10
Posts: 204
Website

Re: LVM2 incorrectly reporting one of my drives are full

That can't be right because sdb and sdc are only 250GB drives so how can I get away with having a 320GB partion when sda3 and sdc1 are not in my LV?  Is there a way to get more details about the status of my LVM setup?

Offline

#4 2011-02-07 13:10:44

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,911

Re: LVM2 incorrectly reporting one of my drives are full

looking at the reports again, my assumption that sda3 and sdc1 were not used in a LV was wrong.

you can try 'vgdisplay -v' 'pvdisplay -v'  and 'lvdisplay -v' to get more info.

I have a simpler setup then you with only 1 LV (home) , but below is the output of those 3 commands on my system :

vgdisplay -v

vgdisplay -v
    Finding all volume groups
    Finding volume group "vg1"
  --- Volume group ---
  VG Name               vg1
  System ID             
  Format                lvm2
  Metadata Areas        4
  Metadata Sequence No  5
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                1
  Open LV               1
  Max PV                0
  Cur PV                4
  Act PV                4
  VG Size               2.27 TiB
  PE Size               4.00 MiB
  Total PE              596148
  Alloc PE / Size       596148 / 2.27 TiB
  Free  PE / Size       0 / 0   
  VG UUID               jP8ZeZ-imFW-BTm0-x26r-P1L2-3dx9-a2Ccqu
   
  --- Logical volume ---
  LV Name                /dev/vg1/lvhome
  VG Name                vg1
  LV UUID                70nxRZ-qb29-XEDV-thKB-jQx6-6pcm-4jyuEc
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                2.27 TiB
  Current LE             596148
  Segments               4
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:0
   
  --- Physical volumes ---
  PV Name               /dev/sda3     
  PV UUID               sHFPdq-Fpi9-rxwT-Xakt-S15P-90S9-7Sfvhc
  PV Status             allocatable
  Total PE / Free PE    47675 / 0
   
  PV Name               /dev/sdb1     
  PV UUID               oUmLMT-q1Ny-EM3w-Ri2P-gLC9-UwTA-kPNMCl
  PV Status             allocatable
  Total PE / Free PE    71541 / 0
   
  PV Name               /dev/sdc1     
  PV UUID               Pt6D85-FsM4-SpRi-X7JJ-xe0J-ehy1-fGpPZE
  PV Status             allocatable
  Total PE / Free PE    238466 / 0
   
  PV Name               /dev/sdd1     
  PV UUID               lQSQgF-zGdP-FrfJ-FGv8-8Xjv-Xviq-2uW0ZT
  PV Status             allocatable
  Total PE / Free PE    238466 / 0

pvdisplay -v

pvdisplay -v
    Scanning for physical volume names
  --- Physical volume ---
  PV Name               /dev/sda3
  VG Name               vg1
  PV Size               186.23 GiB / not usable 1.28 MiB
  Allocatable           yes (but full)
  PE Size               4.00 MiB
  Total PE              47675
  Free PE               0
  Allocated PE          47675
  PV UUID               sHFPdq-Fpi9-rxwT-Xakt-S15P-90S9-7Sfvhc
   
  --- Physical volume ---
  PV Name               /dev/sdb1
  VG Name               vg1
  PV Size               279.46 GiB / not usable 1.63 MiB
  Allocatable           yes (but full)
  PE Size               4.00 MiB
  Total PE              71541
  Free PE               0
  Allocated PE          71541
  PV UUID               oUmLMT-q1Ny-EM3w-Ri2P-gLC9-UwTA-kPNMCl
   
  --- Physical volume ---
  PV Name               /dev/sdc1
  VG Name               vg1
  PV Size               931.51 GiB / not usable 3.19 MiB
  Allocatable           yes (but full)
  PE Size               4.00 MiB
  Total PE              238466
  Free PE               0
  Allocated PE          238466
  PV UUID               Pt6D85-FsM4-SpRi-X7JJ-xe0J-ehy1-fGpPZE
   
  --- Physical volume ---
  PV Name               /dev/sdd1
  VG Name               vg1
  PV Size               931.51 GiB / not usable 3.19 MiB
  Allocatable           yes (but full)
  PE Size               4.00 MiB
  Total PE              238466
  Free PE               0
  Allocated PE          238466
  PV UUID               lQSQgF-zGdP-FrfJ-FGv8-8Xjv-Xviq-2uW0ZT

lvdisplay -v

lvdisplay -v
    Finding all logical volumes
  --- Logical volume ---
  LV Name                /dev/vg1/lvhome
  VG Name                vg1
  LV UUID                70nxRZ-qb29-XEDV-thKB-jQx6-6pcm-4jyuEc
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                2.27 TiB
  Current LE             596148
  Segments               4
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:0

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#5 2011-02-07 17:42:29

vendion
Member
From: Tennessee, USA
Registered: 2010-03-10
Posts: 204
Website

Re: LVM2 incorrectly reporting one of my drives are full

This is what I get from 'vgdisplay -v' and 'lvdisplay -v':

vgdisplay -v
    Finding all volume groups
    Finding volume group "system"
  --- Volume group ---
  VG Name               system
  System ID             
  Format                lvm2
  Metadata Areas        3
  Metadata Sequence No  19
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                3
  Open LV               3
  Max PV                0
  Cur PV                3
  Act PV                3
  VG Size               549.96 GiB
  PE Size               4.00 MiB
  Total PE              140789
  Alloc PE / Size       82988 / 324.17 GiB
  Free  PE / Size       57801 / 225.79 GiB
  VG UUID               PfcLnh-ezIA-ehWO-CTfX-98o4-pgXd-NNJB8E

   --- Logical volume ---
  LV Name                /dev/system/root
  VG Name                system
  LV UUID                QKjbN4-3xO3-bAJC-xgzL-5tdz-92lw-i7jp5w
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                320.00 GiB
  Current LE             81920
  Segments               2
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:0
   
  --- Logical volume ---
  LV Name                /dev/system/swap
  VG Name                system
  LV UUID                5yeEwa-OcX5-tRlJ-6jXQ-ubI5-XMEj-I6Mjul
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                4.00 GiB
  Current LE             1024
  Segments               1
  Allocation             contiguous
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:1

 --- Logical volume ---
  LV Name                /dev/system/home
  VG Name                system
  LV UUID                t41cTt-jMVO-QaHX-keSq-1u96-x1dU-MffUS9
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                176.00 MiB
  Current LE             44
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:2
   
  --- Physical volumes ---
  PV Name               /dev/sda3     
  PV UUID               1Rd2rD-WXPd-4V43-Rn8a-3iq9-Gzr9-KnGBVc
  PV Status             allocatable
  Total PE / Free PE    21553 / 21553
   
  PV Name               /dev/sdb1     
  PV UUID               1SKHYW-q8GQ-mafu-DhHd-Xprk-wxsr-NzPPQ7
  PV Status             allocatable
  Total PE / Free PE    59618 / 0
   
  PV Name               /dev/sdc1     
  PV UUID               5aXwSX-CfqT-dGol-GEyl-2RTJ-WFvP-fycHZX
  PV Status             allocatable
  Total PE / Free PE    59618 / 36248
pvdisplay -v
    Scanning for physical volume names
  --- Physical volume ---
  PV Name               /dev/sda3
  VG Name               system
  PV Size               84.20 GiB / not usable 4.02 MiB
  Allocatable           yes 
  PE Size               4.00 MiB
  Total PE              21553
  Free PE               21553
  Allocated PE          0
  PV UUID               1Rd2rD-WXPd-4V43-Rn8a-3iq9-Gzr9-KnGBVc
   
  --- Physical volume ---
  PV Name               /dev/sdb1
  VG Name               system
  PV Size               232.88 GiB / not usable 673.00 KiB
  Allocatable           yes (but full)
  PE Size               4.00 MiB
  Total PE              59618
  Free PE               0
  Allocated PE          59618
  PV UUID               1SKHYW-q8GQ-mafu-DhHd-Xprk-wxsr-NzPPQ7
   
  --- Physical volume ---
  PV Name               /dev/sdc1
  VG Name               system
  PV Size               232.88 GiB / not usable 673.00 KiB
  Allocatable           yes 
  PE Size               4.00 MiB
  Total PE              59618
  Free PE               36248
  Allocated PE          23370
  PV UUID               5aXwSX-CfqT-dGol-GEyl-2RTJ-WFvP-fycHZX

The only thing I can think of that would cause this, and let me know if my guess is correct, but the bulk of my system is on /dev/sdb1 and the rest is on /dev/sdc1 (going off of the information displayed from the "Total PE", "Free PE", "Allocated PE" from pvdisplay command.

Last edited by vendion (2011-02-07 17:44:03)

Offline

#6 2011-02-08 10:43:51

Ashren
Member
From: Denmark
Registered: 2007-06-13
Posts: 1,229
Website

Re: LVM2 incorrectly reporting one of my drives are full

vendion wrote:

...

Another question I have is why does one of my logical volumes show as /dev/dm-0 instead of /dev/mapper/system-root?

I also noticed this:

[root@namer ~]# ls -l /dev/vgdns/lvroot 
lrwxrwxrwx 1 root root 7 Feb  2 14:40 /dev/vgdns/lvroot -> ../dm-1
[root@namer ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
udev                   10M  184K  9.9M   2% /dev
/dev/dm-1             1.6G  307M  1.2G  21% /
shm                   498M     0  498M   0% /dev/shm
/dev/mapper/vgdns-lvhome
                      3.0G  612M  2.3G  22% /home
/dev/mapper/vgdns-lvsrv
                      3.0G  129M  2.7G   5% /srv
/dev/mapper/vgdns-lvtmp
                      2.0G   69M  1.9G   4% /tmp
/dev/mapper/vgdns-lvusr
                      5.0G  1.3G  3.4G  28% /usr
/dev/mapper/vgdns-lvvar
                      2.0G  741M  1.2G  39% /var
/dev/sda1              92M   20M   67M  24% /boot

An LVM2 bug or arch specific?

Filed bug report:
https://bugs.archlinux.org/task/22813

Last edited by Ashren (2011-02-08 10:59:10)

Use LVM2!

XMobar/XMonad - Click Workspaces :: Blog about Linux (mostly) :: Script for repetitive scrotting :: ISC DHCP Git Hooks

Offline

Pages: 1

Board footer

Powered by FluxBB