On 11 Feb 2015, NeilBrown said: > >> > It might be interesting to see output from >> > >> > rpc.debug -m rpc -s cache >> > cat /proc/net/rpc/nfsd.export/content >> > cat /proc/net/rpc/nfsd.fh/content >> > >> > especially after the problem manifests. >> >> It's manifested right now, as a matter of fact. >> >> # cat /proc/net/rpc/nfsd.export/content >> #path domain(flags) >> /usr/src mutilate.wkstn.nix(rw,no_root_squash,async,wdelay,no_subtree_check,fsid=16,uuid=333950aa:8e3f440a:bc94d0cc:4adae198,sec=1) >> /usr/share/texlive mutilate.wkstn.nix(rw,no_root_squash,async,wdelay,fsid=7,uuid=5cccc224:a92440ee:b4450447:3898c2ec,sec=1) > > You didn't run the "rpcdebug" command first (there is no '.'). > That causes the 'content' files to contain extra information which might be > useful. Ah. That's because of this: /proc/sys/sunrpc/rpc_debug: No such file or directory Looks like I'll need to recompile with CONFIG_SUNRPC_DEBUG to do that. I have a stable kernel upgrade coming up anyway: I'll get that done and see if the problem recurs after the usual round-the-houses reboot... with my luck, it'll go away :/ -- NULL && (void) -- 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
