On Sat, 2010-10-30 at 13:41 -0400, Brian J. Murrell wrote: > On Sun, 2010-10-17 at 14:35 -0400, Trond Myklebust wrote: > > > > Error 127 is EKEYEXPIRED. It means that the RPCSEC_GSS context for at > > least one of your threads has expired. > > > > Sigh... It looks as if we have a really poor handling of that in the > > recovery threads. > > > > Does the following patch help? > > Well, while I don't seem to have had any of the state manager failed > errors, I did have a number of processes blocked in NFS4 today with the > patched kernel running: > > [316999.281908] SysRq : Show Blocked State > [316999.285576] task PC stack pid father > [316999.285576] rhythmbox D f32d1c9c 0 12726 12614 0x00000000 <snip> > > Maybe the above is an unrelated problem? The processes appeared to be waiting for state recovery to complete, but your trace didn't contain any evidence that a state recovery thread was running. Did you over-edit the trace output, or was this really all? Trond -- 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
