A GFS2 file system failed to mount after it was fenced off

Solution In Progress - Updated -

Issue

  • A GFS2 file system failed to mount after it was fenced off.
Nov 25 08:54:01 node42 kernel: GFS2: fsid=: Trying to join cluster "lock_dlm", "mycluster:lv_file_updn_gfs"
Nov 25 08:54:01 node42 kernel: GFS2: fsid=mycluster:lv_file_updn_gfs.2: Joined cluster. Now mounting FS...
Nov 25 08:54:02 node42 kernel: GFS2: fsid=mycluster:lv_file_updn_gfs.2: can't mount journal #2
Nov 25 08:54:02 node42 kernel: GFS2: fsid=mycluster:lv_file_updn_gfs.2: there are only 2 journals (0 - 1)
  • An error occurred mounting a gfs2 filesystem:
Sep 14 12:03:48 node42 kernel: GFS2: fsid=: Trying to join cluster "lock_dlm", "mycluster:lv_gfs2"
Sep 14 12:03:53 node42 kernel: GFS2: fsid=mycluster:lv_gfs2.2: Joined cluster. Now mounting FS...
Sep 14 12:06:50 node42 kernel: INFO: task mount.gfs2:3019 blocked for more than 120 seconds.
Sep 14 12:06:54 node42 kernel: GFS2: fsid=mycluster:lv_gfs2.2: can't mount journal #2
Sep 14 12:06:54 node42 kernel: GFS2: fsid=mycluster:lv_gfs2.2: there are only 2 journals (0 - 1)
Sep 14 12:06:54 node42 gfs_controld[2837]: cpg_mcast_joined error 12 handle 1e7ff52100000001 mount_done

Environment

  • Red Hat Enterprise Linux Server 5, 6 (with the High Availability and Resilient Storage Add Ons)
  • A Global Filesystem 2(GFS2)

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