All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] GFS2: mark the journal idle to fix ro mounts
Date: Fri, 24 Apr 2015 16:18:27 -0400 (EDT)	[thread overview]
Message-ID: <417680874.6659471.1429906707391.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1429888385-25449-1-git-send-email-bmarzins@redhat.com>

----- Original Message -----
> When gfs2 was mounted read-only and then unmounted, it was writing a
> header block to the journal in the syncing gfs2_log_flush() call from
> kill_sb(). This is because the journal was not being marked as idle
> until the first log header was written out, and on a read-only mount
> there never was a log header written out. Since the journal was not
> marked idle, gfs2_log_flush() was writing out a header lock to make
> sure it was empty during the sync.  Not only did this cause IO to a
> read-only filesystem, but the journalling isn't completely initialized
> on read-only mounts, and so gfs2 was writing out the wrong sequence
> number in the log header.
> 
> Now, the journal is marked idle on mount, and gfs2_log_flush() won't
> write out anything until there starts being transactions to flush.
> 
> Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com>

Hi,

ACK
Makes sense to me.

Regards,

Bob Peterson
Red Hat File Systems



  reply	other threads:[~2015-04-24 20:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-24 15:13 [Cluster-devel] [PATCH] GFS2: mark the journal idle to fix ro mounts Benjamin Marzinski
2015-04-24 20:18 ` Bob Peterson [this message]
2015-04-27 10:01 ` Steven Whitehouse
2015-04-27 17:31   ` Benjamin Marzinski
2015-04-28  9:44     ` Steven Whitehouse
2015-05-01 14:45 ` Bob Peterson

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=417680874.6659471.1429906707391.JavaMail.zimbra@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.