Bug 806900 - multiple entries of "inode.weight=1" under "xlator.performance.io-cache.priv" section in statedump log file
Summary: multiple entries of "inode.weight=1" under "xlator.performance.io-cache.priv"...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: shishir gowda
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 817967
TreeView+ depends on / blocked
 
Reported: 2012-03-26 13:07 UTC by Shwetha Panduranga
Modified: 2015-12-01 16:45 UTC (History)
3 users (show)

Fixed In Version: glusterfs-3.4.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-24 17:22:28 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)
statedump log file (261.56 KB, application/octet-stream)
2012-03-26 13:07 UTC, Shwetha Panduranga
no flags Details

Description Shwetha Panduranga 2012-03-26 13:07:54 UTC
Created attachment 572752 [details]
statedump log file

Description of problem:
when statedump was taken on glusterfs client process, it reported huge number of <inode.weight=1> key value pairs under "xlator.performance.io-cache.priv"  section

There are 1672 <inode.weight=1> entries in the attached statedump log file

[03/26/12 - 22:27:11 root@APP-CLIENT1 /]# grep "inode.weight" /tmp/glusterdump.22698.dump | wc -l
1672

Version-Release number of selected component (if applicable):
mainline

How reproducible:
often

Steps to Reproduce:
1.create a replicate volume (1X3).Start the volume
2.create fuse, nfs mounts from client. Start write operations on all the mounts.
3.perform graph change (performance.read-ahead/ performance.write-behind on/off)
4.take statedump of glusterfs client process.

Comment 1 Anand Avati 2012-04-01 13:16:39 UTC
CHANGE: http://review.gluster.com/3014 (performance/io-cache: Enhance state-dump output) merged in master by Vijay Bellur (vijay)

Comment 2 Shwetha Panduranga 2012-04-12 09:25:38 UTC
Verified on 3.3.0qa34. Works fine.


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