On May 17, 2012, at 9:12 AM, Stuart Kendrick wrote: >> My starting guess is that there is some task on that client that has dirtied the pages of one of the files in the directory you are trying to list. A GETATTR is required to flush outstanding writes to a file so the server can provide size and mtime attributes that reflect the last most recent write to that file. >> >> Possible work-arounds: You can reduce the dirty_ratio setting on the client to force it to starting flushing outstanding writes sooner, you can change the writing applications to use synchronous writes (or flush manually), or you can alter your "ls" command so that it doesn't require a GETATTR for each file. >> > How might I replicate this? > > I'm trying a continuous write to a file ... but 'ls -l' remains snappy. The file must reside in the directory you are listing, and it should be very large. Typically dd'ing zeroes into a large file is a good way to starve non-writers. > #!/bin/bash > while [ true ] > cp foo.1 foo.2 > echo Do it again > done -- Chuck Lever chuck[dot]lever[at]oracle[dot]com -- 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
