Bug 801689 - Incorrect last-cache-validation-time in statedump
Summary: Incorrect last-cache-validation-time in statedump
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: io-cache
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Vijay Bellur
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 817967
TreeView+ depends on / blocked
 
Reported: 2012-03-09 07:10 UTC by Anush Shetty
Modified: 2013-07-24 17:53 UTC (History)
2 users (show)

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

Attachments (Terms of Use)

Description Anush Shetty 2012-03-09 07:10:18 UTC 
Description of problem: The last-cache-validation-time in xlator.performance.io-cache.priv in statedump have the value reset.


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


How reproducible: Consistently


Steps to Reproduce:
1. kill -USR1 <pid-of-glusterfs>

Actual results:

[]
page_size=131072
cache_size=33554432
cache_used=0
inode_count=2
cache_timeout=1
min-file-size=0
max-file-size=0
inode.weight=1
last-cache-validation-time=1970-01-01 05:30:00.000000
inode.weight=1
last-cache-validation-time=1970-01-01 05:30:00.000000
Comment 1 Anand Avati 2012-03-12 06:52:20 UTC 
CHANGE: http://review.gluster.com/2912 (Print non-zero timestamps in statedump) merged in master by Vijay Bellur (vijay)
Comment 2 Anush Shetty 2012-05-14 10:53:17 UTC 
Fixed now.
Note You need to log in before you can comment on or make changes to this bug.