Bug 762015 (GLUSTER-283) - booster aborts complaining the refcount of iobuf is not zero during glusterfs_umount_all.
Summary: booster aborts complaining the refcount of iobuf is not zero during glusterfs...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-283
Product: GlusterFS
Classification: Community
Component: libglusterfsclient
Version: 2.0.6
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Raghavendra G
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-09-25 08:20 UTC by Raghavendra G
Modified: 2009-11-23 11:56 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: RTNR
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Raghavendra G 2009-09-25 08:20:46 UTC 
some of the iobufs in pool will be cached by io-cache and hence refcount will not be zero. Hence the assertion of ref being zero in __iobuf_arena_destroy fails. Commenting out iobuf_pool_destroy during fini, till we introduce proper cleanup in all translators, thereby allowing io-cache to release the buffers it has held.
Comment 1 Anand Avati 2009-09-28 22:57:16 UTC 
PATCH: http://patches.gluster.com/patch/1495 in master (libglusterfsclient: don't destroy the iobuf pool during fini.)
Comment 2 Anand Avati 2009-09-28 22:57:24 UTC 
PATCH: http://patches.gluster.com/patch/1494 in release-2.0 (libglusterfsclient: don't destroy the iobuf pool during fini.)
Note You need to log in before you can comment on or make changes to this bug.