From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH V2] GFS2: Don't withdraw on partial rindex entries
Date: Tue, 26 Jan 2010 14:20:07 +0000 [thread overview]
Message-ID: <1264515607.3047.20.camel@localhost> (raw)
In-Reply-To: <20100125172323.GH17440@ether.msp.redhat.com>
Hi,
Now in the -nmw git tree. Thanks,
Steve.
On Mon, 2010-01-25 at 11:23 -0600, Benjamin Marzinski wrote:
> ince gfs2 writes the rindex file a block at a time, and releases the
> exclusive lock after each block, it is possible that another process
> will grab the lock in the middle of the write. Since rindex entries are
> not an even divisor of blocks, that other process may see partial
> entries. On grows, this is fine. The process can simply ignore the the
> partial entires. Previously, the code withdrew when it saw partial
> entries. Now it simply ignores them.
>
> Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com>
> ---
> fs/gfs2/rgrp.c | 5 -----
> 1 file changed, 5 deletions(-)
>
> Index: gfs2-2.6-nmw/fs/gfs2/rgrp.c
> ===================================================================
> --- gfs2-2.6-nmw.orig/fs/gfs2/rgrp.c
> +++ gfs2-2.6-nmw/fs/gfs2/rgrp.c
> @@ -591,11 +591,6 @@ static int gfs2_ri_update(struct gfs2_in
> u64 rgrp_count = ip->i_disksize;
> int error;
>
> - if (do_div(rgrp_count, sizeof(struct gfs2_rindex))) {
> - gfs2_consist_inode(ip);
> - return -EIO;
> - }
> -
> clear_rgrpdi(sdp);
>
> file_ra_state_init(&ra_state, inode->i_mapping);
>
prev parent reply other threads:[~2010-01-26 14:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 17:23 [Cluster-devel] [PATCH V2] GFS2: Don't withdraw on partial rindex entries Benjamin Marzinski
2010-01-26 14:20 ` 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=1264515607.3047.20.camel@localhost \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).