On Wed, Jul 27, 2011 at 03:54:49PM -0400, Bryan Schumaker wrote: > > Any chance to figure out if the file you hit the printk with was one > > that got either recently added or moved when you hit it? (I can't > > follow the nfs code enough to check if it prints the first or second hit > > of the same cookie) > > It should be printing on the second hit of a cookie. But looking closer at it it only prints the directory name and not that of any of the matching cookies, making it pretty useless to debug any problem. (and it makes my previous question to Justin look stupid..). But so far I still stick to my previous theory that this sounds like a directory offset getting reused. How is cache invalidation for the array supposed to work? And maybe more importantly, given that he can only reproduce it with a .38 client did any bugs get fixed in that code recently that might lead to issues with the cache invalidation? -- 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
