Bug 762972 (GLUSTER-1240)

Summary: DVM: after graph change, inodes should resolve to new inode-table
Product: [Community] GlusterFS Reporter: Amar Tumballi <amarts>
Component: fuseAssignee: Amar Tumballi <amarts>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: low    
Version: mainlineCC: gluster-bugs, vraman
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Amar Tumballi 2010-07-28 11:24:48 UTC 
Currently, we are referring inode pointers directly as 'nodeid' and even if graph changes, we are referring to old graph's inode, which will be sort of stale.

Hence we have to bring in something like server-resolve, where if the current inode which is resolved is of old graph, we have to resolve the inode corresponding to new graph.
Comment 1 Anand Avati 2010-08-12 02:24:41 UTC 
PATCH: http://patches.gluster.com/patch/4026 in master (fuse resolve related changes)
Comment 2 Vijay Bellur 2010-09-23 11:51:01 UTC 
PATCH: http://patches.gluster.com/patch/4941 in master (fuse-resolve: remove stale code)
Comment 3 Anand Avati 2010-11-16 04:46:03 UTC 
PATCH: http://patches.gluster.com/patch/5710 in master (fuse: dentry create time inode resolution fixes)