[lkml]   [2009]   [Jan]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Patch in this message
    SubjectRe: spurious -ENOSPC on XFS

    On Sun, 18 Jan 2009, Christoph Hellwig wrote:

    > On Tue, Jan 13, 2009 at 11:28:58PM -0500, Mikulas Patocka wrote:
    > > The result must not depend on magic timer values. If it does, you end up
    > > with undebbugable nondeterministic failures.
    > >
    > > Why don't you change that 500ms wait to "wait until the flush finishes"?
    > > That would be correct.
    > Yes, this probably would better. Could I motivate you to come up with
    > a patch for that?


    I looked at the source and found out that it uses sync_blockdev for
    syncing --- but sync_blockdev writes only metadata buffers, it doesn't
    touch inodes and pages and doesn't resolve delayed allocations. So it
    really doesn't sync anything.

    I replaced it with correct syncing of all inodes. With this patch it
    passes my testcase (no more spurious -ENOSPCs), but it still isn't
    correct, there is that 500ms delay --- if the machine was so overloaded
    that it couldn't sync withing 500ms, you still get spurious -ENOSPC.

    There are notions about possible deadlocks (the syncer may lock against
    the process that is waiting for the sync to finish), that's why removing
    that 500ms delay isn't that easy as it seems. I don't have XFS knowledge
    to check for the deadlocks, it should be done by XFS developers. Also,
    when you resolve the deadlocks and drop the timeout, replace WB_SYNC_NONE
    with WB_SYNC_ALL in this patch.



    Properly sync when the filesystem runs out of space because of delayed
    allocation overaccounting.

    Note that sync_blockdev writes just dirty metadata buffers, it doesn't touch
    inodes or data buffers --- so it had no effect.

    WB_SYNC_ALL should be used instead of WB_SYNC_NONE, but WB_SYNC_ALL gets worse
    results --- it is likely because WB_SYNC_ALL sync locks against the process
    doing the write, stalling the whole sync. This needs to be further investigated
    by XFS developers. Also, further investigation is needed to remove that

    Signed-off-by: Mikulas Patocka <>

    fs/xfs/linux-2.6/xfs_sync.c | 8 +++++++-
    1 file changed, 7 insertions(+), 1 deletion(-)

    Index: linux-2.6.29-rc1-devel/fs/xfs/linux-2.6/xfs_sync.c
    --- linux-2.6.29-rc1-devel.orig/fs/xfs/linux-2.6/xfs_sync.c 2009-01-20 20:13:32.000000000 +0100
    +++ linux-2.6.29-rc1-devel/fs/xfs/linux-2.6/xfs_sync.c 2009-01-20 20:24:31.000000000 +0100
    @@ -446,7 +446,13 @@ xfs_flush_device_work(
    void *arg)
    struct inode *inode = arg;
    - sync_blockdev(mp->m_super->s_bdev);
    + struct writeback_control wbc = {
    + .sync_mode = WB_SYNC_NONE,
    + .range_start = 0,
    + .range_end = LLONG_MAX,
    + .nr_to_write = LONG_MAX,
    + };
    + generic_sync_sb_inodes(mp->m_super, &wbc);

     \ /
      Last update: 2009-01-20 20:43    [W:0.024 / U:47.208 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site