RHEL 6 Resilient Storage cluster node using GFS2 crashes after reporting "original: gfs2_glock_nq_init+0x16/0x40 [gfs2]"

Solution In Progress - Updated -

Issue

  • My cluster node crashed several times with output reporting "original: gfs2_glock_nq_init+0x16/0x40 [gfs2]" and "new: gfs2_glock_nq_init+0x16/0x40 [gfs2]
Aug 17 08:46:29 node1 kernel: original: gfs2_glock_nq_init+0x16/0x40 [gfs2] 
Aug 17 08:46:29 node1 kernel: pid: 13890 
Aug 17 08:46:29 node1 kernel: lock type: 2 req lock state : 1 
Aug 17 08:46:29 node1 kernel: new: gfs2_glock_nq_init+0x16/0x40 [gfs2] 
Aug 17 08:46:29 node1 kernel: pid: 13890 
Aug 17 08:46:29 node1 kernel: lock type: 2 req lock state : 1 
Aug 17 08:46:29 node1 kernel: G: s:EX n:2/151013c f:Iqob t:EX d:EX/0 a:0 v:0 r:5 m:200 
Aug 17 08:46:29 node1 kernel: H: s:EX f:H e:0 p:13890 [strmqm] gfs2_glock_nq_init+0x16/0x40

Environment

  • Red Hat Enterprise Linux (RHEL) 6 with the Resilient Storage Add-On
  • GFS2
  • Issue observed using kernel-2.6.32-573.el6

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
Close

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