Bug 428119 - slab error in kmem_cache_destroy(): cache `dlm_conn': Can't free all objects
slab error in kmem_cache_destroy(): cache `dlm_conn': Can't free all objects
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel (Show other bugs)
5.3
All Linux
high Severity high
: rc
: ---
Assigned To: David Teigland
Red Hat Kernel QE team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-01-09 06:55 EST by Christine Caulfield
Modified: 2009-09-03 12:51 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-01-17 12:07:19 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)
Patch to fix (352 bytes, patch)
2008-01-10 03:52 EST, Christine Caulfield
no flags Details | Diff

  None (edit)
Description Christine Caulfield 2008-01-09 06:55:33 EST
Description of problem:

Systems often display this message at shutdown:
"slab error in kmem_cache_destroy(): cache `dlm_conn': Can't free all objects"

Version-Release number of selected component (if applicable):
Probably since 5.2


How reproducible:
Easily.

Steps to Reproduce:
1. Start up cluster with clvmd. 3 nodes for preference
2. Shutdown some nodes
  
Actual results:
one or more nodes will display the above message

it gets worse...
If you stop all DLM lockspaces and attempt to restart them you get that
message plus

"kmem_cache_create: duplicate cache dlm_conn"

and the DLM won't start. this needs a node reboot.

Expected results:
The DLM should shut down cleanly.

Additional info:

This is because the ->othercon structures are not being freed. With all the
othercon patching that went on a while ago it seems like a bit of the patch has
got lost.
Comment 1 Christine Caulfield 2008-01-10 03:52:41 EST
Created attachment 291245 [details]
Patch to fix

This patch has been sent to Steve for inclusion upstream.
Comment 2 Kiersten (Kerri) Anderson 2008-01-17 11:39:21 EST
Proposing for inclusion in 5.2 release.  Patch available and will affect
customers who are trying to stop and start the clusters.
Comment 3 Christine Caulfield 2008-01-17 12:07:19 EST
Closing this bug as the patch was only missing from upstream (and is now
included there). 

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