[Cluster-devel] [GFS2 PATCH 1/3] Obtaining no_formal_ino from directory entry

[S. Wendy Cheng]

GFS2 lookup code doesn't ask for inode shared glock. This implies during 
in-memory inode creation for existing file, GFS2 will not disk-read in 
the inode contents. This leaves no_formal_ino un-initialized during 
lookup time. The un-initialized no_formal_ino is subsequently encoded 
into file handle. Clients will get ESTALE error whenever it tries to 
access these files.

-- Wendy

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 02_gfs2_specsfs.patch
Type: text/x-patch
Size: 6104 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20070625/99c4bdb0/attachment.bin>