[lkml]   [2009]   [Jan]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] async: Don't call async_synchronize_full_special() while holding sb_lock
    Arjan van de Ven wrote:
    > > - removing a million files and queuing all of the
    > > deletes in the async queues....
    > the async code throttles at 32k outstanding.
    > Yes 32K is arbitrary, but if you delete a million files fast, all but the
    > first few thousand are
    > synchronous.


    If I call unlink() a thousand times and then call fsync() on the
    parent directories covering files I've unlinked... I expect the
    deletes to be committed to disk when the last fsync() has returned. I
    require that a crash and restart will not see the files. Several
    kinds of transactional software and even some shell scripts expect this.

    Will these asynchronous deletes break the guaranteed
    commit-of-the-delete provided by fsync() on the parent directory?

    -- Jamie

     \ /
      Last update: 2009-01-12 03:35    [W:0.018 / U:31.936 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site