Re: "write failed.. No space left", "Failed to write VG", and "Failed to write a MDA"

Inbox <jimhaddad46@xxxxxxxxx> · Sun, 3 Jun 2018 15:21:54 -0700

Sorry to be mailing again, think this info helps though...

On Sun, Jun 3, 2018 at 1:13 PM, Inbox <jimhaddad46@xxxxxxxxx> wrote:
...
# lvcreate -V200G lvm/disk3thin -n test3
...
  /dev/sdh3: write failed after 24064 of 24576 at 4993488961536: No space left on device
... 
# lvremove lvm/test3
  /dev/sdh3: write failed after 24064 of 24576 at 4993488961536: No space left on device
  WARNING: Failed to write an MDA of VG lvm.
  /dev/sdg3: write failed after 24064 of 24576 at 4993488961536: No space left on device
  WARNING: Failed to write an MDA of VG lvm.
  /dev/sdf3: write failed after 24064 of 24576 at 4993488961536: No space left on device
  WARNING: Failed to write an MDA of VG lvm.

fdisk -l  shows sdf3, sdg3, and sdh3, sdg3, are 4993488985600 bytes.

After some reading, I'm guessing mda means metadata area.

If LVM is trying to write mda2 at 4993488961536, there's only 24064 bytes left in the partition, which is exactly where it's saying the write is failing.

I did use "--pvmetadatacopies 2" when running pvcreate.

So, am I right that it's trying to write more than 24k of metadata at the end of the disk, but there's only 24k left at the end of the disk for a metadata copy?

If so, where the other locations for metadata (both the main one, and the first copy) only 24k?  Did I lose metadata in those areas?  Did it overwrite what was after the metadata area?

Where do I go from here?

# pvdisplay --maps /dev/sdh3
  --- Physical volume ---
  PV Name               /dev/sdh3
  VG Name               lvm
  PV Size               4.54 TiB / not usable 2.19 MiB
  Allocatable           yes (but full)
  PE Size               4.00 MiB
  Total PE              1190540
  Free PE               0
  Allocated PE          1190540
  PV UUID               BK8suJ-dqiy-mdK4-IyUH-aeRR-TPUo-3Dj6JG

  --- Physical Segments ---
  Physical extent 0 to 127:
    Logical volume      /dev/lvm/disk1thin_tmeta
    Logical extents     32 to 159
  Physical extent 128 to 4095:
    Logical volume      /dev/lvm/swap1
    Logical extents     0 to 3967
  Physical extent 4096 to 4127:
    Logical volume      /dev/lvm/lvol0_pmspare
    Logical extents     0 to 31
  Physical extent 4128 to 132127:
    Logical volume      /dev/lvm/disk1thin_tdata
    Logical extents     0 to 127999
  Physical extent 132128 to 132159:
    Logical volume      /dev/lvm/disk1thin_tmeta
    Logical extents     0 to 31
  Physical extent 132160 to 1190539:
    Logical volume      /dev/lvm/disk1thin_tdata
    Logical extents     128000 to 1186379

Those physical extents translate to beginning/ending bytes (4MiB PE size) of:

0	532676608
536870912	17175674880
17179869184	17309892608
17314086912	554180804608
554184998912	554315022336
554319216640	4993482489856

Disk size (4993488961536) - last physical extent ending byte (4993482489856 + 4*1024*1024 assuming worst case scenario here, the x856 is the starting byte of the last extent) still leaves 2277376 bytes, way more than 24k.
_______________________________________________
linux-lvm mailing list
linux-lvm@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/