On Wed, Sep 14, 2011 at 08:27:59AM +0200, Tim wrote: > >> /proc/sys/fs/nfs/nlm_grace_period > >> This is the part I don't understand what it is for. I read it has to > >> be shrunk too (I set it to 10 - which works). Standard value is 0. > > > NLM (used with NFSv2/v3) works a little differently: instead of the clients polling at regular intervals, the server calls back to the clients to notify them that it has rebooted. But there's still this grace period, which is the length of time the NLM server waits for the clients to act on the notifications by sending lock reclaims. > > > It affects v4 as well, because the v4 server can't end its grace period before the NLM server does: if it did, v4 clients could rush in and start doing new locks before v2/v3 clients had the chance to reclaim all of theirs. > > So if I only use NFSv4, I can set this to 1 second? Or would 0 be better? Should be safe. (Without looking at the code I don't remember if 0 is allowed or has some special meaning.) Some day we should start automatically turning off v2/v3-only stuff in the v4-only case, it just hasn't been a priority yet. --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
