On Fri, Sep 13, 2013 at 01:32:47PM +0200, Joschi Brauchle wrote: > After three days of testing the NFS server *with* rpc.gssd running > with multiple NFS clients, we made the following observation: > > The hangs on "utime()" calls have **not** disappeared by simply starting > rpc.gssd on the server. The problem persists! > > I seems like > a) on machines that are already connected to the NFS server when > rpc.gssd is started, the hangs dissappear *mostly*. That is, running > the utime-test-program causes about 1 spurious hang every 10 > minutes. > b) on machines that connect to the NFS server at a later time > (rpc.gssd already running on the server), the hangs seem appear > every "utime()" call. > > The server emits spurious "RPC: AUTH_GSS upcall timed out. Please > check user daemon is running." messages, although rpc.gssd is > running. This may or may not be related, as this message may also be > caused by clients where the root user access NFS shared with a > "host/<hostname>" credential. > > The output of "rpcdebug -m nfsd -s proc" to pastebin.com. Get it with > pbget http://pastebin.com/N34r5kWE > > The IP of the newly connected host is: 192.168.109.154 and its > SETCLIENTID call was logged. Unfortunately, this log was created > while *many* other NFS clients were connected, hence it may not be > too useful. > > I'd be very grateful for any help or instructions on > debugging/fixing this problem. NFSv4.0 callbacks have just broken for a while, I think; I'll look into it. Meanwhile you should be able to work around this by disabling leases on the server (so, "echo 0 >/proc/sys/fs/leases-enable" before starting nfsd). (Or if you're more daring and running a very recent upstream kernel, switching to NFSv4.1 should work too.) --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
