From: Robert Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [RHEL5 PATCH] GFS2: bz 222302: gfs2 knows of directories which it chooses not to display
Date: Thu, 11 Jan 2007 13:25:00 -0600 [thread overview]
Message-ID: <45A68F0C.7000202@redhat.com> (raw)
This is for bugzilla bug bz #222302:
Moving a virtual IP from node to node between two NFS-over-GFS2
servers was causing one of the GFS2 servers to become confused and
reference a deleted inode. The problem was due to vfs dentries that did
not reference the gfs2_dops and therefore didn't call the gfs2 revalidate
code to revalidate a dentry after a directory had been deleted & recreated.
This patch is a crosswrite from a RHEL4 bug found in GFS1 as
bz #190756 and it is against the latest -nmw git tree.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gfs2.patch
Type: text/x-patch
Size: 647 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20070111/8b1fce41/attachment.bin>
next reply other threads:[~2007-01-11 19:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 19:25 Robert Peterson [this message]
2007-01-12 11:39 ` [Cluster-devel] Re: [RHEL5 PATCH] GFS2: bz 222302: gfs2 knows of directories which it chooses not to display 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=45A68F0C.7000202@redhat.com \
--to=rpeterso@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.