Bug 806900
| Summary: | multiple entries of "inode.weight=1" under "xlator.performance.io-cache.priv" section in statedump log file | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Shwetha Panduranga <shwetha.h.panduranga> | ||||
| Component: | glusterd | Assignee: | shishir gowda <sgowda> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | mainline | CC: | gluster-bugs, nsathyan, vbellur | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | glusterfs-3.4.0 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-07-24 17:22:28 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 817967 | ||||||
| Attachments: |
|
||||||
CHANGE: http://review.gluster.com/3014 (performance/io-cache: Enhance state-dump output) merged in master by Vijay Bellur (vijay) Verified on 3.3.0qa34. Works fine. |
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.