From mboxrd@z Thu Jan 1 00:00:00 1970 From: S. Wendy Cheng Date: Mon, 25 Jun 2007 21:14:53 -0400 Subject: [Cluster-devel] [GFS2 PATCH 1/3] Obtaining no_formal_ino from directory entry Message-ID: <4680688D.6060608@redhat.com> List-Id: To: cluster-devel.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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: