LVM Logical Volume Geometry Size Problem: Difference between revisions

From UNIX Systems Administration
Jump to navigation Jump to search
No edit summary
Line 12: Line 12:
#: <tt>'''# vgchange -an <volume group>'''</tt>
#: <tt>'''# vgchange -an <volume group>'''</tt>
# Rescan all SCSI Host Adapters.
# Rescan all SCSI Host Adapters.
#: <tt>'''# echo '- - -' > /sys/class/scsi_host/<host#>/scan'''</tt>
#: <tt>'''# echo '- - -' > /sys/class/scsi_host/host<#>/scan'''</tt>
# Rescan all SCSI block devices associated with the volume group
# Rescan all SCSI block devices associated with the volume group
#: <tt>'''# echo 1 > /sys/block/<block device>/device/rescan'''</tt>
#: <tt>'''# echo 1 > /sys/block/<block device>/device/rescan'''</tt>

Revision as of 03:00, 28 January 2022

Error Messages Observed

The following messages appear in dmesg after an unsuccessful activation of a volume groups logical volumes

device-mapper: table: <major>:<minor>: <block device> too small for target: start=<sector>, len=<sector>, dev_size=<size>
kernel: EXT4-fs (dm-9): bad geometry: block count <number> exceeds size of device (<number> blocks)

The following messages appear after a vgimport on a volume group

device-mapper: resume ioctl on failed: Invalid argument
Unable to resume <volume group>-<logical volume> (253:23)

Fix Procedure

  1. Deactivate the volume group's logical volumes
    # vgchange -an <volume group>
  2. Rescan all SCSI Host Adapters.
    # echo '- - -' > /sys/class/scsi_host/host<#>/scan
  3. Rescan all SCSI block devices associated with the volume group
    # echo 1 > /sys/block/<block device>/device/rescan
  4. Resize all physical volumes associated with the volume group
    # pvscan
    # pvresize /dev/<block device>
  5. Activate the volume group's logical volumes
    # vgchange -ay <volume group>

Further Reading