From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] GFS2: Write out dirty inode metadata in delayed deletes
Date: Fri, 21 Sep 2012 11:56:04 +0100 [thread overview]
Message-ID: <1348224964.2746.37.camel@menhir> (raw)
In-Reply-To: <20120920145258.GB5182@ether.msp.redhat.com>
Hi,
Thanks for the patch, I'll push it into the -nmw tree shortly,
Steve.
On Thu, 2012-09-20 at 09:52 -0500, Benjamin Marzinski wrote:
> If a dirty GFS2 inode was being deleted but was in use by another node, its
> metadata was not getting written out before GFS2 checked for dirty buffers in
> gfs2_ail_flush(). GFS2 was relying on inode_go_sync() to write out the
> metadata when the other node tried to free the file, but it failed the error
> check before it got that far. This patch writes out the metadata before calling
> gfs2_ail_flush()
>
> Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com>
> ---
> fs/gfs2/super.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> Index: gfs2-3.0-nmw/fs/gfs2/super.c
> ===================================================================
> --- gfs2-3.0-nmw.orig/fs/gfs2/super.c
> +++ gfs2-3.0-nmw/fs/gfs2/super.c
> @@ -1545,6 +1545,11 @@ static void gfs2_evict_inode(struct inod
>
> out_truncate:
> gfs2_log_flush(sdp, ip->i_gl);
> + if (test_bit(GLF_DIRTY, &ip->i_gl->gl_flags)) {
> + struct address_space *metamapping = gfs2_glock2aspace(ip->i_gl);
> + filemap_fdatawrite(metamapping);
> + filemap_fdatawait(metamapping);
> + }
> write_inode_now(inode, 1);
> gfs2_ail_flush(ip->i_gl, 0);
>
>
prev parent reply other threads:[~2012-09-21 10:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 14:52 [Cluster-devel] [PATCH] GFS2: Write out dirty inode metadata in delayed deletes Benjamin Marzinski
2012-09-21 10:56 ` Steven Whitehouse [this message]
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=1348224964.2746.37.camel@menhir \
--to=swhiteho@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.