On 12/5/09 1:12 PM, "Trond Myklebust" <Trond.Myklebust@xxxxxxxxxx> wrote: > On Sat, 2009-12-05 at 12:55 -0800, Labiaga, Ricardo wrote: >> Tried with this patch but it didn't make a difference. > > You are still seeing RPC calls with 0 session ids? > Yes, right after the session is destroyed, and before it's recreated. The original RPC that got the BAD_SESSION error keeps on trying. After the session is recreated, the same RPC is issued (with the same sequenceID) but with the new sessionID. This time it fails with SEQ_MISORDERED. This repeats indefinitely until the process is manually interrupted. >> I haven't tried applying the second cleanup patch yet since it >> didn't apply cleanly on top of nfs-for-next. Is this the branch you >> used? > > I've pushed out all patches (including the cleanup patch) onto > nfs-for-next now... > Got it, I was able to apply both patches. The results above are with both patches. - ricardo -- 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
