LVM Logical Volume Geometry Size Problem: Difference between revisions

From UNIX Systems Administration
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
These messages appear in dmesg after an unsuccessful activation of a volume groups logical volumes.
These messages appear in dmesg after an unsuccessful activation of a volume groups logical volumes.
<br /><tt>'''device-mapper: table: <major>:<minor>: <block device> too small for target: start=<sector>, len=<sector>, dev_size=<size>'''</tt>
:<br /><tt>'''device-mapper: table: <major>:<minor>: <block device> too small for target: start=<sector>, len=<sector>, dev_size=<size>'''</tt>
<br /><tt>'''kernel: EXT4-fs (dm-9): bad geometry: block count <number> exceeds size of device (<number> blocks)'''</tt>
:<br /><tt>'''kernel: EXT4-fs (dm-9): bad geometry: block count <number> exceeds size of device (<number> blocks)'''</tt>


# Deactivate the volume group's logical volumes.
# Deactivate the volume group's logical volumes.

Revision as of 13:39, 11 December 2015

These 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)
  1. Deactivate the volume group's logical volumes.
    1. # vgchange -an <volume group>
  1. Rescan all SCSI block devices associated with the volume group.
    1. # echo 1 > /sys/block/<block device>/device/rescan
  1. Resize all physical volumes associated with the volume group.
    1. # pvscan
    2. # pvresize /dev/<block device>
  1. Activate the volume group's logical volumes.
    1. # vgchange -ay <volume group>