cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH] GFS2: Re-add a call to log_flush_wait when flushing the journal
Date: Wed, 12 Mar 2014 14:48:15 +0000	[thread overview]
Message-ID: <1394635695.2729.61.camel@menhir> (raw)
In-Reply-To: <489569871.13173225.1394634856079.JavaMail.zimbra@redhat.com>

Hi,

On Wed, 2014-03-12 at 10:34 -0400, Bob Peterson wrote:
> Hi,
> 
> Upstream commit 34cc178 changed a line of code from calling function
> log_flush_commit to calling log_write_header. This had the effect of
> eliminating a call to function log_flush_wait. That causes the journal
> to skip over log headers, which results in multiple wrap points,
> which itself leads to infinite loops in journal replay, both in the
> kernel code and fsck.gfs2 code. This patch re-adds that call.
> 
> Regards,
> 
> Bob Peterson
> Red Hat File Systems
> 
Well spotted! Looks good. I've added this to the -nmw tree as well.
Thanks,

Steve.

> Signed-off-by: Bob Peterson <rpeterso@redhat.com> 
> ---
> diff --git a/fs/gfs2/log.c b/fs/gfs2/log.c
> index edbd461..4a14d50 100644
> --- a/fs/gfs2/log.c
> +++ b/fs/gfs2/log.c
> @@ -702,6 +702,7 @@ void gfs2_log_flush(struct gfs2_sbd *sdp, struct gfs2_glock *gl)
>  	gfs2_log_flush_bio(sdp, WRITE);
>  
>  	if (sdp->sd_log_head != sdp->sd_log_flush_head) {
> +		log_flush_wait(sdp);
>  		log_write_header(sdp, 0);
>  	} else if (sdp->sd_log_tail != current_tail(sdp) && !sdp->sd_log_idle){
>  		atomic_dec(&sdp->sd_log_blks_free); /* Adjust for unreserved buffer */
> 




      reply	other threads:[~2014-03-12 14:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1832141140.13172193.1394634781361.JavaMail.zimbra@redhat.com>
2014-03-12 14:34 ` [Cluster-devel] [GFS2 PATCH] GFS2: Re-add a call to log_flush_wait when flushing the journal Bob Peterson
2014-03-12 14:48   ` 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=1394635695.2729.61.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 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).