LVM commands hanging in cluster, after resizing the VG using uderlying paths

Solution Unverified - Updated -

Issue

  • Filesystems in cluster unresponsive

  • I was extending a logical volume on 1 of the 4 nodes in the cluster and I think I specified an incorrect LUN. Since I did this some of the filesystems on all of the nodes have become un-responsive. LVM is also unresponsive. Need urgent P1 assistance to fix LVM so that I can restore from backup.

  • I was meant to be choosing a newly presented multipathed LUN but in error I think I chose the underlying device file belonging to an EMC powerpath LUN. I didn't get as far as extending the filesystem as I realised what I'd done when running the lvextend command as it aborted. The commands I ran were:

pvcreate dev/sdbn1
vgextend vgXX dev/sdbn1
lvextend -L 200G /dev/mapper/vgXX-uXXvol

Environment

  • Red Hat Enterprise Linux 5.10
  • Red Hat Enterprise Linux 5 with High Availability or Resilient Storage Add-on

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.