Messages in this thread | | | Date | Tue, 29 Sep 2009 16:47:20 -0400 | From | Chris Mason <> | Subject | Re: [PATCH] bdi_sync_writeback should WB_SYNC_NONE first |
| |
On Fri, Sep 25, 2009 at 10:10:14AM -0400, Chris Mason wrote: > At unmount time, we do writeback in two stages. First we call > sync_filesystems with wait == 0, and then we call it with wait == 1. > > When wait == 1, WB_SYNC_ALL is used. WB_SYNC_ALL will pass wait == 1 to > the filesystem write_inode function if the inode was I_DIRTY_SYNC, and > the filesystem write_inode function is then expected to commit the > running transaction. > > The new bdi threads try to keep this two stage writeback, but the > problem is that they do it by calling bdi_writeback_all, which just > kicks a few procs here and there and returns. >
And I can't reproduce any problems with mainline today. ENOTABUG.
-chris
| |