On Mon, Jul 08, 2013 at 10:08:05AM +0200, Sven Geggus wrote: > Monday Monday, so good to me :) > > On Friday, 5. Jul 2013 22:34, J. Bruce Fields wrote: > > > Hm, might be interesting to see what mountd's doing too: > > > > strace -p $(pidof rpc.svcgssd) -s4096 -e trace=open,close,read,write Argh--I said "mountd", then I forgot to replace the rpc.svcgssd in the cut-n-pasted commandline; should have been: strace -p $(pidof rpc.mountd) -s4096 -e trace=open,close,read,write > > OK, output attached. While reading this output I recogniced, that I > overlooked the following error-messages from rpc.svcgssd and rpc.mountd: > > Jul 8 09:53:38 vnfsrv rpc.svcgssd[2914]: ERROR: GSS-API: error in gss_free_lucid_sec_context(): GSS_S_NO_CONTEXT (No context has been established) - Unknown error > Jul 8 09:53:38 vnfsrv rpc.svcgssd[2914]: WARN: failed to free lucid sec context > Jul 8 09:53:38 vnfsrv rpc.mountd[2927]: qword_eol: fprintf failed: errno 22 (Invalid argument) > > > Hm, maybe this gid upcall? Does the following (probably not completely > > right) help? > > Yes, we are getting there. While the strange messages from rpc.svcgssd > persist, the mount now seems to work again after your patch has been > applied. Anyway. OK, that more or less solves the mystery, though the strace output might still be interesting. --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
