"...0d0cea2424ae97b27447dc64a7dbfae83c036c45b403392f0e8ba.png" did not exist on "a8c8d7c683419d059e302373afc6998244f5f60f"
writeback: merely wakeup flusher thread if work allocation fails for WB_SYNC_NONE
Since it's an opportunistic writeback and not a data integrity action, don't punt to blocking writeback. Just wakeup the thread and it will flush old data. Acked-by:Jan Kara <jack@suse.cz> Signed-off-by:
Christoph Hellwig <hch@infradead.org> Signed-off-by:
Jens Axboe <jens.axboe@oracle.com>
Loading
Please register or sign in to comment