On Mon, 2011-10-24 at 13:17 +0000, David Flynn wrote: > * Trond Myklebust (Trond.Myklebust@xxxxxxxxxx) wrote: > > We should in principle be able to recover a BAD_STATEID error by running > > the state recovery thread. It's a shame that the machine was rebooted, > > but does your syslog trace perhaps show any state recovery thread > > errors? > > There were no other nfs related messages reported between the initial > blocked task and rebooting the machine later. Additionally, there were > no nfs related messages from bootup of the machine until the blocked > task. > > One thing that may be of interest is that the user in question with the > blocked task had hit their quota hard limit. (It was the same user that > had the issue i reported earlier too on the same filesystem). > > Kind regards, > ..david I'm assuming then that your network trace showed no sign of any OPEN calls of that particular file, just retries of the WRITE? -- Trond Myklebust Linux NFS client maintainer NetApp Trond.Myklebust@xxxxxxxxxx www.netapp.com -- 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
