[Cluster-devel] [GFS2 PATCH 1/3] Obtaining no_formal_ino from directory entry
Steven Whitehouse
swhiteho at redhat.com
Wed Jun 27 03:02:26 UTC 2007
Hi,
On Mon, 2007-06-25 at 21:14 -0400, S. Wendy Cheng wrote:
> 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
>
Generally this looks good. Please don't add back the _host structure
though - just add an extra no_formal_ino argument to the lookup function
which is a u64,
Steve.
More information about the Cluster-devel
mailing list