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. Hmm. 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 -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
