cluster service using HA-LVM tagging fails to recover after 'dm-X too small for target' errors in RHEL 6

Solution Verified - Updated -

Issue

  • Service with lvm resources failed and then could not be recovered on backup node because of 'dm-X too small for target' errors from device-mapper:
Jun 10 13:33:29 node2 kernel: device-mapper: table: 253:162: dm-46 too small for target: start=315648000, len=20971520, dev_size=41925120
Jun 10 13:33:29 node2 kernel: device-mapper: table: 253:191: dm-46 too small for target: start=303065088, len=12582912, dev_size=41925120
Jun 10 13:33:29 node2 kernel: device-mapper: table: 253:202: dm-46 too small for target: start=238946304, len=5398528, dev_size=41925120
Jun 10 13:33:38 node2 rgmanager[5052]: [lvm] Failed second attempt to activate myVG
Jun 10 13:33:38 node2 rgmanager[13202]: start on lvm "myVG" returned 1 (generic error)
Jun 10 13:33:38 node2 rgmanager[13202]: #68: Failed to start service:nfs-service; return value: 1

Environment

  • Red Hat Enterprise Linux (RHEL) 6 with the High Availability Add On
  • HA-LVM using tagging

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content