LVM and No Space Left On Device

llin · 07-28-2008, 06:35 AM

A LV (XFS) is stuck at the 1.2TB mark and won't accept new data even though there's space available.

df -h (working LVs not shown):

Code:

Filesystem            Size  Used Avail Use% Mounted on
/dev/hda1             149G   77G   73G  52% /
/dev/mapper/fileserver-lv1
                      1.7T  1.2T  450G  73% /LV1

df -ih:

Code:

Filesystem            Inodes   IUsed   IFree IUse% Mounted on
/dev/hda1                  0       0       0    -  /
/dev/mapper/fileserver-lv1
                        1.7G     82K    1.7G    1% /LV1

pvdisplay:

Code:

  --- Physical volume ---
  PV Name               /dev/sda1
  VG Name               fileserver
  PV Size               698.64 GB / not usable 2.34 MB
  Allocatable           yes (but full)
  PE Size (KByte)       4096
  Total PE              178850
  Free PE               0
  Allocated PE          178850
  PV UUID               8aLaVo-P2lo-BbEL-k9hI-WTmw-2TeI-A1GWvh

  --- Physical volume ---
  PV Name               /dev/sdb1
  VG Name               fileserver
  PV Size               698.64 GB / not usable 2.34 MB
  Allocatable           yes (but full)
  PE Size (KByte)       4096
  Total PE              178850
  Free PE               0
  Allocated PE          178850
  PV UUID               qtueHm-czJI-elKt-QZy3-53TU-uMe1-fgVJ0g

  --- Physical volume ---
  PV Name               /dev/sdc1
  VG Name               fileserver
  PV Size               698.64 GB / not usable 2.34 MB
  Allocatable           yes
  PE Size (KByte)       4096
  Total PE              178850
  Free PE               24959
  Allocated PE          153891
  PV UUID               fxZwEA-l8YJ-S6xA-EiNu-Z2hs-vvrY-fZ5mAf

vgdisplay:

Code:

  VG Name               fileserver
  System ID
  Format                lvm2
  Metadata Areas        3
  Metadata Sequence No  17
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                5
  Open LV               5
  Max PV                0
  Cur PV                3
  Act PV                3
  VG Size               2.05 TB
  PE Size               4.00 MB
  Total PE              536550
  Alloc PE / Size       511591 / 1.95 TB
  Free  PE / Size       24959 / 97.50 GB
  VG UUID               8h13tn-3yee-KlSI-kyiL-3ms2-dsjM-uAUj2t

lvdisplay:

Code:

  --- Logical volume ---
  LV Name                /dev/fileserver/lv1
  VG Name                fileserver
  LV UUID                3uYtpi-ope5-ISt9-638A-rrA7-JId0-30o59r
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                1.62 TB
  Current LE             424551
  Segments               3
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:2

From initial research the PE size mattered in LVM1 but not LVM2.

jay73 · 07-28-2008, 06:47 PM

So maybe it is the filesystem that is to blame? Run out of inodes or something like that? Consult xfs_check.

syg00 · 07-28-2008, 11:46 PM

Quote:

Originally Posted by llin

From initial research the PE size mattered in LVM1 but not LVM2.

You think ???. If

Quote:

Total PE 178850

indicates an intrinsic limit (I don't know, I'm hypothesising) then the PE size will have a *real* big say in how much space you get to paddle around in. Especially when immediately followed by

Quote:

Free PE 0

llin · 07-29-2008, 12:16 AM

Quote:

Run out of inodes or something like that?

df -i shows copious amounts of inodes.

Quote:

Originally Posted by syg00

You think ???. If
indicates an intrinsic limit (I don't know, I'm hypothesising) then the PE size will have a *real* big say in how much space you get to paddle around in.

Was referring to the pvmetadatasize option (4 MB), not the physical volumes themselves. That the first two volumes show 0 free PEs is normal as they've been filled with data (with the third volume getting close)

syg00 · 07-29-2008, 01:04 AM

Ahhh sorry, my bad. I'd crawl back under my rock.