From: Bill O'Donnell <billodo@redhat.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Brian Foster <bfoster@redhat.com>, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 1/9] xfs: sync lazy sb accounting on quiesce of read-only mounts
Date: Thu, 21 Jan 2021 11:17:12 -0600 [thread overview]
Message-ID: <20210121171712.GA1372309@redhat.com> (raw)
In-Reply-To: <20210121164933.GA1282159@magnolia>
On Thu, Jan 21, 2021 at 08:49:33AM -0800, Darrick J. Wong wrote:
> On Thu, Jan 21, 2021 at 09:08:27AM -0600, Bill O'Donnell wrote:
> > On Wed, Jan 06, 2021 at 12:41:19PM -0500, Brian Foster wrote:
> > > xfs_log_sbcount() syncs the superblock specifically to accumulate
> > > the in-core percpu superblock counters and commit them to disk. This
> > > is required to maintain filesystem consistency across quiesce
> > > (freeze, read-only mount/remount) or unmount when lazy superblock
> > > accounting is enabled because individual transactions do not update
> > > the superblock directly.
> > >
> > > This mechanism works as expected for writable mounts, but
> > > xfs_log_sbcount() skips the update for read-only mounts. Read-only
> > > mounts otherwise still allow log recovery and write out an unmount
> > > record during log quiesce. If a read-only mount performs log
> > > recovery, it can modify the in-core superblock counters and write an
> > > unmount record when the filesystem unmounts without ever syncing the
> > > in-core counters. This leaves the filesystem with a clean log but in
> > > an inconsistent state with regard to lazy sb counters.
> > >
> > > Update xfs_log_sbcount() to use the same logic
> > > xfs_log_unmount_write() uses to determine when to write an unmount
> > > record. We can drop the freeze state check because the update is
> > > already allowed during the freezing process and no context calls
> > > this function on an already frozen fs. This ensures that lazy
> > > accounting is always synced before the log is cleaned. Refactor this
> > > logic into a new helper to distinguish between a writable filesystem
> > > and a writable log. Specifically, the log is writable unless the
> > > filesystem is mounted with the norecovery mount option, the
> > > underlying log device is read-only, or the filesystem is shutdown.
> > >
> > > Signed-off-by: Brian Foster <bfoster@redhat.com>
> > > Reviewed-by: Gao Xiang <hsiangkao@redhat.com>
> >
> > works for me.
> > Reviewed-by: Bill O'Donnell <billodo@redhat.com>
>
> Does this also apply to the v3 series that Brian just sent?
I only used this patch 1/9, as that was all I was focusing on.
>
> --D
>
> >
> > > ---
> > > fs/xfs/xfs_log.c | 28 ++++++++++++++++++++--------
> > > fs/xfs/xfs_log.h | 1 +
> > > fs/xfs/xfs_mount.c | 3 +--
> > > 3 files changed, 22 insertions(+), 10 deletions(-)
> > >
> > > diff --git a/fs/xfs/xfs_log.c b/fs/xfs/xfs_log.c
> > > index fa2d05e65ff1..b445e63cbc3c 100644
> > > --- a/fs/xfs/xfs_log.c
> > > +++ b/fs/xfs/xfs_log.c
> > > @@ -347,6 +347,25 @@ xlog_tic_add_region(xlog_ticket_t *tic, uint len, uint type)
> > > tic->t_res_num++;
> > > }
> > >
> > > +bool
> > > +xfs_log_writable(
> > > + struct xfs_mount *mp)
> > > +{
> > > + /*
> > > + * Never write to the log on norecovery mounts, if the block device is
> > > + * read-only, or if the filesystem is shutdown. Read-only mounts still
> > > + * allow internal writes for log recovery and unmount purposes, so don't
> > > + * restrict that case here.
> > > + */
> > > + if (mp->m_flags & XFS_MOUNT_NORECOVERY)
> > > + return false;
> > > + if (xfs_readonly_buftarg(mp->m_log->l_targ))
> > > + return false;
> > > + if (XFS_FORCED_SHUTDOWN(mp))
> > > + return false;
> > > + return true;
> > > +}
> > > +
> > > /*
> > > * Replenish the byte reservation required by moving the grant write head.
> > > */
> > > @@ -886,15 +905,8 @@ xfs_log_unmount_write(
> > > {
> > > struct xlog *log = mp->m_log;
> > >
> > > - /*
> > > - * Don't write out unmount record on norecovery mounts or ro devices.
> > > - * Or, if we are doing a forced umount (typically because of IO errors).
> > > - */
> > > - if (mp->m_flags & XFS_MOUNT_NORECOVERY ||
> > > - xfs_readonly_buftarg(log->l_targ)) {
> > > - ASSERT(mp->m_flags & XFS_MOUNT_RDONLY);
> > > + if (!xfs_log_writable(mp))
> > > return;
> > > - }
> > >
> > > xfs_log_force(mp, XFS_LOG_SYNC);
> > >
> > > diff --git a/fs/xfs/xfs_log.h b/fs/xfs/xfs_log.h
> > > index 58c3fcbec94a..98c913da7587 100644
> > > --- a/fs/xfs/xfs_log.h
> > > +++ b/fs/xfs/xfs_log.h
> > > @@ -127,6 +127,7 @@ int xfs_log_reserve(struct xfs_mount *mp,
> > > int xfs_log_regrant(struct xfs_mount *mp, struct xlog_ticket *tic);
> > > void xfs_log_unmount(struct xfs_mount *mp);
> > > int xfs_log_force_umount(struct xfs_mount *mp, int logerror);
> > > +bool xfs_log_writable(struct xfs_mount *mp);
> > >
> > > struct xlog_ticket *xfs_log_ticket_get(struct xlog_ticket *ticket);
> > > void xfs_log_ticket_put(struct xlog_ticket *ticket);
> > > diff --git a/fs/xfs/xfs_mount.c b/fs/xfs/xfs_mount.c
> > > index 7110507a2b6b..a62b8a574409 100644
> > > --- a/fs/xfs/xfs_mount.c
> > > +++ b/fs/xfs/xfs_mount.c
> > > @@ -1176,8 +1176,7 @@ xfs_fs_writable(
> > > int
> > > xfs_log_sbcount(xfs_mount_t *mp)
> > > {
> > > - /* allow this to proceed during the freeze sequence... */
> > > - if (!xfs_fs_writable(mp, SB_FREEZE_COMPLETE))
> > > + if (!xfs_log_writable(mp))
> > > return 0;
> > >
> > > /*
> > > --
> > > 2.26.2
> > >
> >
>
next prev parent reply other threads:[~2021-01-21 17:19 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 17:41 [PATCH 0/9] xfs: rework log quiesce to cover the log Brian Foster
2021-01-06 17:41 ` [PATCH 1/9] xfs: sync lazy sb accounting on quiesce of read-only mounts Brian Foster
2021-01-06 22:50 ` Allison Henderson
2021-01-07 19:06 ` Darrick J. Wong
2021-01-11 17:38 ` Christoph Hellwig
2021-01-12 14:55 ` Brian Foster
2021-01-12 18:20 ` Christoph Hellwig
2021-01-21 15:08 ` Bill O'Donnell
2021-01-21 16:49 ` Darrick J. Wong
2021-01-21 17:17 ` Bill O'Donnell [this message]
2021-01-06 17:41 ` [PATCH 2/9] xfs: lift writable fs check up into log worker task Brian Foster
2021-01-06 22:50 ` Allison Henderson
2021-01-07 18:34 ` Darrick J. Wong
2021-01-07 19:53 ` Brian Foster
2021-01-07 21:28 ` Darrick J. Wong
2021-01-13 15:24 ` Christoph Hellwig
2021-01-06 17:41 ` [PATCH 3/9] xfs: separate log cleaning from log quiesce Brian Foster
2021-01-06 22:50 ` Allison Henderson
2021-01-07 19:07 ` Darrick J. Wong
2021-01-13 15:30 ` Christoph Hellwig
2021-01-06 17:41 ` [PATCH 4/9] xfs: cover the log during " Brian Foster
2021-01-07 19:04 ` Darrick J. Wong
2021-01-07 19:53 ` Brian Foster
2021-01-19 17:51 ` Darrick J. Wong
2021-01-19 15:35 ` Christoph Hellwig
2021-01-06 17:41 ` [PATCH 5/9] xfs: don't reset log idle state on covering checkpoints Brian Foster
2021-01-07 19:30 ` Darrick J. Wong
2021-01-07 20:01 ` Brian Foster
2021-01-06 17:41 ` [PATCH 6/9] xfs: fold sbcount quiesce logging into log covering Brian Foster
2021-01-07 19:31 ` Darrick J. Wong
2021-01-06 17:41 ` [PATCH 7/9] xfs: remove duplicate wq cancel and log force from attr quiesce Brian Foster
2021-01-07 19:38 ` Darrick J. Wong
2021-01-06 17:41 ` [PATCH 8/9] xfs: remove xfs_quiesce_attr() Brian Foster
2021-01-07 19:39 ` Darrick J. Wong
2021-01-06 17:41 ` [PATCH 9/9] xfs: cover the log on freeze instead of cleaning it Brian Foster
2021-01-07 19:39 ` Darrick J. Wong
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=20210121171712.GA1372309@redhat.com \
--to=billodo@redhat.com \
--cc=bfoster@redhat.com \
--cc=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
/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).