From: S. Wendy Cheng <wcheng@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH 1/3] Obtaining no_formal_ino from directory entry
Date: Mon, 25 Jun 2007 21:14:53 -0400 [thread overview]
Message-ID: <4680688D.6060608@redhat.com> (raw)
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>
next reply other threads:[~2007-06-26 1:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-26 1:14 S. Wendy Cheng [this message]
2007-06-26 1:18 ` [Cluster-devel] [GFS2 PATCH 2/3] Obtaining no_formal_ino from directory entry S. Wendy Cheng
2007-06-27 3:02 ` [Cluster-devel] [GFS2 PATCH 1/3] " Steven Whitehouse
2007-06-27 5:15 ` [Cluster-devel] [GFS2 PATCH 2/3] " S. Wendy Cheng
2007-06-27 5:25 ` S. Wendy Cheng
2007-06-27 13:13 ` Steven Whitehouse
2007-06-27 21:07 ` Wendy Cheng
2007-06-27 22:49 ` Steven Whitehouse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4680688D.6060608@redhat.com \
--to=wcheng@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.