Bug 762972 (GLUSTER-1240) - DVM: after graph change, inodes should resolve to new inode-table
Summary: DVM: after graph change, inodes should resolve to new inode-table
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-1240
Product: GlusterFS
Classification: Community
Component: fuse
Version: mainline
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Amar Tumballi
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-28 11:24 UTC by Amar Tumballi
Modified: 2015-12-01 16:45 UTC (History)
2 users (show)

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

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

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)
Note You need to log in before you can comment on or make changes to this bug.