On Thu, Dec 12, 2013 at 05:42:44PM +0100, Sander Klein wrote: > On , J. Bruce Fields wrote: > >That sounds like somewhat of an extreme setup, and I suspect the > >current > >behavior is by design, but I agree that we should fix it. I'm not > >volunteering for now.... > > Ow dear, I never thought that this would classified as an extreme > setup :-) . Eh, maybe it's not. > >I think what happens is that exportfs flushes the kernel's export cache > >at which point every use of an uncached export triggers an upcall to > >mountd. That upcall is probably visible in the strace as a read of a > >file descriptor associated with /proc/net/sunrpc/nfsd.fh/content. > > > >That upcall is handled by nfs-utils/utils/mountd/cache.c:nfsd_fh(), > >which is given a filehandle fragment identifying the filesystem in > >question and has to match it to an export. > > > >That's done by match_fsid(). Which does do a stat of the export path, > >but not of all the devices.... That's probably happening in one of the > >libblkid calls in uuid_by_path()? I wonder if there's something wrong > >with libblkid configuration or with the way we're using it? > > Is there any way I can help getting this fixed? My coding skills are > limited but I am very willing to help in any way I can. I wonder if ltrace could help determine if libblkid is where most of those stat's are coming from (and if so, which calls)? May also be worth reading up on libblkid (man libblkid, etc.) and checking your configuration to make sure there's nothing obvious broken there. (If so, maybe the libblkid commandline tools would exhibit the same problem?) --b. -- 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
