linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 3/4] xfs: remove leftover CoW reservations when remounting ro
Date: Mon, 18 Dec 2017 19:49:11 -0800	[thread overview]
Message-ID: <20171219034911.GB11975@magnolia> (raw)
In-Reply-To: <20171219001755.GJ4094@dastard>

On Tue, Dec 19, 2017 at 11:17:55AM +1100, Dave Chinner wrote:
> On Fri, Dec 15, 2017 at 09:11:31AM -0800, Darrick J. Wong wrote:
> > From: Darrick J. Wong <darrick.wong@oracle.com>
> > 
> > When we're remounting the filesystem readonly, remove all CoW
> > preallocations prior to going ro.  If the fs goes down after the ro
> > remount, we never clean up the staging extents, which means xfs_check
> > will trip over them on a subsequent run.  Practically speaking, the
> > next mount will clean them up too, so this is unlikely to be seen.
> > 
> > Found by adding clonerange to fsstress and running xfs/017.
> > 
> > Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> > ---
> >  fs/xfs/xfs_super.c |    8 ++++++++
> >  1 file changed, 8 insertions(+)
> > 
> > 
> > diff --git a/fs/xfs/xfs_super.c b/fs/xfs/xfs_super.c
> > index f663022..7b6d150 100644
> > --- a/fs/xfs/xfs_super.c
> > +++ b/fs/xfs/xfs_super.c
> > @@ -1369,6 +1369,14 @@ xfs_fs_remount(
> >  
> >  	/* rw -> ro */
> >  	if (!(mp->m_flags & XFS_MOUNT_RDONLY) && (*flags & MS_RDONLY)) {
> > +		/* Get rid of any leftover CoW reservations... */
> > +		cancel_delayed_work_sync(&mp->m_cowblocks_work);
> > +		error = xfs_icache_free_cowblocks(mp, NULL);
> > +		if (error) {
> > +			xfs_force_shutdown(mp, SHUTDOWN_CORRUPT_INCORE);
> > +			return error;
> > +		}
> 
> On rw->ro do we start the m_cowblocks_work back up?

Assuming you meant to ask about ro->rw, then yes it should get started
back up the next time something sets the cowblocks tag.  I'm not opposed
to starting it back up directly from the ro->rw handler.

> What about when we freeze the filesystem - shouldn't we clean
> up the cow blocks there, too? We've tried hard in the past to make
> freeze and rw->ro exactly the same so that if the system is powered
> down while frozen it comes up almost entirely clean just like a
> ro-remount in shutdown....

I don't see a hard requirement to clean them up at freeze time, though
we certainly can do it for consistency's sake.

> And, FWIW, this makes ro->rw and thaw essentially the same, too.

Noted.

> Cheers,
> 
> Dave.
> -- 
> Dave Chinner
> david@fromorbit.com

  reply	other threads:[~2017-12-19  3:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-15 17:11 [PATCH 0/4] xfs: more reflink fixes Darrick J. Wong
2017-12-15 17:11 ` [PATCH 1/4] xfs: track cowblocks separately in i_flags Darrick J. Wong
2017-12-19  0:12   ` Dave Chinner
2017-12-21 13:36   ` Christoph Hellwig
2017-12-15 17:11 ` [PATCH 2/4] xfs: don't be so eager to clear the cowblocks tag on truncate Darrick J. Wong
2017-12-19  0:12   ` Dave Chinner
2017-12-21 13:37   ` Christoph Hellwig
2017-12-15 17:11 ` [PATCH 3/4] xfs: remove leftover CoW reservations when remounting ro Darrick J. Wong
2017-12-19  0:17   ` Dave Chinner
2017-12-19  3:49     ` Darrick J. Wong [this message]
2017-12-19  4:37       ` Dave Chinner
2017-12-19  4:53         ` Darrick J. Wong
2017-12-19  6:46           ` Dave Chinner
2017-12-19 19:00             ` Darrick J. Wong
2017-12-19 20:55               ` Dave Chinner
2017-12-19 21:08   ` [PATCH v2 " Darrick J. Wong
2017-12-21 13:38     ` Christoph Hellwig
2017-12-15 17:11 ` [PATCH 4/4] xfs: set cowblocks tag for direct cow writes too Darrick J. Wong
2017-12-19  0:18   ` Dave Chinner
2017-12-21 13:39   ` Christoph Hellwig
2017-12-19 21:09 ` [PATCH 5/4] xfs: clean up cow mappings during fs data freeze Darrick J. Wong
2017-12-21 13:39   ` Christoph Hellwig

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=20171219034911.GB11975@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=david@fromorbit.com \
    --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).