Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 675270 - GFS2: Fails to clear glocks during unmount
GFS2: Fails to clear glocks during unmount
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel (Show other bugs)
6.1
Unspecified Unspecified
high Severity unspecified
: rc
: ---
Assigned To: Steve Whitehouse
Cluster QE
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-02-04 13:32 EST by Abhijith Das
Modified: 2011-05-23 16:39 EDT (History)
2 users (show)

See Also:
Fixed In Version: kernel-2.6.32-117.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-05-23 16:39:14 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Patch to fix the issue (440 bytes, patch)
2011-02-04 13:39 EST, Steve Whitehouse
no flags Details | Diff


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2011:0542 normal SHIPPED_LIVE Important: Red Hat Enterprise Linux 6.1 kernel security, bug fix and enhancement update 2011-05-19 07:58:07 EDT

  None (edit)
Description Abhijith Das 2011-02-04 13:32:37 EST
Description of problem:
While testing quotacheck, I found that gfs2 reported the following messages on the console during unmount/rmmod. I was updating a bunch of quotas and immediately unmounting the fs and attempting to remove the module.

 G:  s:EX n:8/23b2 f:lDpIq t:UN d:UN/2000 a:0 r:2
 G:  s:EX n:8/21e5 f:lDprIq t:UN d:UN/6000 a:0 r:3
 G:  s:SH n:8/2b f:lDpIq t:UN d:UN/11000 a:0 r:2
 G:  s:EX n:8/1cfc f:lDprIq t:UN d:UN/15000 a:0 r:3
 G:  s:UN n:8/5da f:Iq t:UN d:EX/0 a:0 r:0
slab error in kmem_cache_destroy(): cache `gfs2_glock(aspace)': Can't free all objects
Pid: 4832, comm: rmmod Not tainted 2.6.32 #1
Call Trace:
 [<ffffffff811537cb>] kmem_cache_destroy+0xbb/0xf0
 [<ffffffffa0a60946>] exit_gfs2_fs+0x84/0x97 [gfs2]
 [<ffffffff810a4824>] sys_delete_module+0x194/0x260
 [<ffffffff8100b172>] system_call_fastpath+0x16/0x1b
slab error in kmem_cache_destroy(): cache `gfs2_glock': Can't free all objects
Pid: 4832, comm: rmmod Not tainted 2.6.32 #1
Call Trace:
 [<ffffffff811537cb>] kmem_cache_destroy+0xbb/0xf0
 [<ffffffffa0a60952>] exit_gfs2_fs+0x90/0x97 [gfs2]
 [<ffffffff810a4824>] sys_delete_module+0x194/0x260
 [<ffffffff8100b172>] system_call_fastpath+0x16/0x1b
Comment 2 Steve Whitehouse 2011-02-04 13:39:09 EST
Created attachment 477088 [details]
Patch to fix the issue

This was an omission from the vfs scale patch which needs to be fixed as soon as possible.
Comment 3 RHEL Product and Program Management 2011-02-04 13:50:36 EST
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has 
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed 
products. This request is not yet committed for inclusion in an Update release.
Comment 4 Abhijith Das 2011-02-05 00:07:19 EST
Verified that with the patch in comment#2, I no longer see the glock/slab messages mentioned above. Posting to rhkernel-list for inclusion in rhel6.1
Comment 5 Aristeu Rozanski 2011-02-18 17:20:36 EST
Patch(es) available on kernel-2.6.32-117.el6
Comment 8 Nate Straz 2011-04-08 07:19:51 EDT
This has not showed up in recent regression runs with kernel-2.6.32-128.el6.
Comment 9 errata-xmlrpc 2011-05-23 16:39:14 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2011-0542.html

Note You need to log in before you can comment on or make changes to this bug.