From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: [PATCH 5/5] xfs: fix xfs_quiesce_data
Date: Mon, 11 May 2009 16:15:11 -0400 [thread overview]
Message-ID: <20090511201511.GB14195@infradead.org> (raw)
In-Reply-To: <4A071F06.8040106@sandeen.net>
On Sun, May 10, 2009 at 01:37:58PM -0500, Eric Sandeen wrote:
> Christoph Hellwig wrote:
>
> > We need to do a synchronous xfs_sync_fsdata to make sure the superblock
> > actually is on disk when we return. While we're at it also remove the
> > superflous SYNC_BDFLUSH flag to xfs_sync_inodes, and move the xfs_filestream_flush
> > call later [hch: why? seems unrelated].
>
> What makes SYNC_BDFLUSH "superfluous?" ... oh ... because nothing in
> that callchain below ever looks for it. Could we make that more obvious
> in the changelog?
Ok.
> I guess I too would like a reason for the filestream_flush move
> somewhere in the changelog...
Hehe, maybe Dave can chime in. Or I can test if it actually affects
anything and maybe move it out to another patch. The lack of
reliability of the filesystreams tests doesn't make this any easier to
test.
>
> Adding the SYNC_WAIT looks good to me though :)
>
> -Eric
>
> >
> > Index: linux-2.6/fs/xfs/linux-2.6/xfs_sync.c
> > ===================================================================
> > --- linux-2.6.orig/fs/xfs/linux-2.6/xfs_sync.c 2009-04-26 10:46:17.112949525 +0200
> > +++ linux-2.6/fs/xfs/linux-2.6/xfs_sync.c 2009-04-26 10:48:19.713979813 +0200
> > @@ -323,16 +323,16 @@ xfs_quiesce_data(
> > int error;
> >
> > /* push non-blocking */
> > - xfs_sync_inodes(mp, SYNC_DELWRI|SYNC_BDFLUSH);
> > + xfs_sync_inodes(mp, SYNC_DELWRI);
> > XFS_QM_DQSYNC(mp, SYNC_BDFLUSH);
> > - xfs_filestream_flush(mp);
> >
> > - /* push and block */
> > + /* push and block till complete */
> > xfs_sync_inodes(mp, SYNC_DELWRI|SYNC_WAIT|SYNC_IOWAIT);
> > XFS_QM_DQSYNC(mp, SYNC_WAIT);
> > + xfs_filestream_flush(mp);
> >
> > /* write superblock and hoover up shutdown errors */
> > - error = xfs_sync_fsdata(mp, 0);
> > + error = xfs_sync_fsdata(mp, SYNC_WAIT);
> >
> > /* flush data-only devices */
> > if (mp->m_rtdev_targp)
> >
> > _______________________________________________
> > xfs mailing list
> > xfs@oss.sgi.com
> > http://oss.sgi.com/mailman/listinfo/xfs
> >
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
---end quoted text---
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-05-11 20:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-26 14:03 [PATCH 0/5] fix sync (test 182, grub) Christoph Hellwig
2009-04-26 14:03 ` [PATCH 1/5] xfs: remove ->write_super and stop maintaining ->s_dirt Christoph Hellwig
2009-05-10 16:25 ` Eric Sandeen
2009-05-10 16:30 ` Eric Sandeen
2009-05-10 17:37 ` Eric Sandeen
2009-04-26 14:03 ` [PATCH 2/5] xfs: cleanup ->sync_fs Christoph Hellwig
2009-05-10 17:51 ` Eric Sandeen
2009-05-11 20:11 ` Christoph Hellwig
2009-04-26 14:03 ` [PATCH 3/5] xfs: make inodes dirty before issuing I/O Christoph Hellwig
2009-05-10 18:02 ` Eric Sandeen
2009-04-26 14:03 ` [PATCH 4/5] xfs: make sure xfs_sync_fsdata covers the log Christoph Hellwig
2009-05-10 18:29 ` Eric Sandeen
2009-04-26 14:03 ` [PATCH 5/5] xfs: fix xfs_quiesce_data Christoph Hellwig
2009-05-10 18:37 ` Eric Sandeen
2009-05-11 20:15 ` Christoph Hellwig [this message]
2009-06-04 9:45 ` Dave Chinner
2009-06-05 10:41 ` Christoph Hellwig
2009-05-06 9:33 ` [PATCH 0/5] fix sync (test 182, grub) 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=20090511201511.GB14195@infradead.org \
--to=hch@infradead.org \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.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