On Fri, May 29, 2009 at 02:36:46PM -0400, Trond Myklebust wrote: > That is most likely to be a consequence of poor mtime resolution on the > server (i.e. the directory mtime failing to change because the file > creation occurred within < 1 second of the 'rm'), combined with negative > lookup caching. As in "ls --full-time" shows 0 for the fractional second part? Hrm, I thought newer ext3 had nanosecond mtime, but it seems not... > Try using the '-olookupcache=positive' or '-olookupcache=none' mount > options (requires a relatively recent version of nfs-utils). After backporting nfs-utils, either of those options seem to this particular case work as desired. Excellent! I guess all of the attribute-caching-related options are unrelated to this case. Is this consistent with older operation and that of other OSes? It might be a little surprising for some (me) when "noac" still ends up doing some caching. Thanks, Simon- -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
