Devices under GFS2 filesystems cause all processes accessing them to hang on Red Hat Enterprise Linux

Solution Verified - Updated -

Issue

  • Somehow a gfs2 file system got corrupt.
  • Running blkid <dev> -c /dev/null on the device with the corrupted file system hangs indefinitely.  The process is shown in defunct (D) state.
  • blkid /dev/mapper/VolStorage01-cluster_data -c /dev/null

Environment

  • Red Hat Enterprise Linux (RHEL), including:
    • Red Hat Enterprise Linux 5 (RHEL5) Advanced Platform
    • Red Hat Enterprise Linux 6 with Resilient Storage Add-on
  • Red Hat Cluster Suite cluster with at least 2 nodes
  • GFS2 filesystem mounted on at least one node
    • Mount options for errors are default, or errors=withdraw.  Problem will not occur if errors=panic is configured.
    • Filesystem corruption was detected and the filesystem was withdrawn.

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