| commit | ccfeb506231348a3c60ab0fdb5753a574653e3c0 | [log] [tgz] |
|---|---|---|
| author | Trond Myklebust <Trond.Myklebust@netapp.com> | Sat Jan 13 02:28:12 2007 -0500 |
| committer | Trond Myklebust <Trond.Myklebust@netapp.com> | Sat Feb 03 15:35:04 2007 -0800 |
| tree | 17e2261c396d927e389c7f018008e5537bc27ddb | |
| parent | ab91f264cfbafd079dcb1bd02e9803c2dd65de19 [diff] |
NFS: Fix up "rm -rf"... When a file is being scheduled for deletion by means of the sillyrename mechanism, it makes sense to start out writeback of the dirty data as soon as possible in order to ensure that the delete can occur. Examples of cases where this is an issue include "rm -rf", which will busy-wait until the file is closed, and the sillyrename completes. Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>