Myklebust, Trond <Trond.Myklebust@...> writes: > > I use kernel 3.7.1 from kernel.org which has the patches included, > > which should fix the problems (I checked the source code). But: > > I get "NFS: nfs4_reclaim_open_state: Lock reclaim failed!" on the > > client, which mounts home over nfs4. > > I get senseless network traffic (50MB/s on my gigabit network). > > Finally I get Kernel Ops on the Server sometimes. > > Lock reclaiming is not guaranteed to succeed; it all depends on why the > lock was lost in the first place. Did the server restart, or did a > network partition occur? Was some other process able to take that lock > (or even delete the file, doh!), before your client could reclaim it? > > That said, if the server is Oopsing, then you have a broken server. I'd > suggest posting that Oops to this list first. > Thanks for the hint, the server was really broken! The power supply of the server had some broken capacitors. With a new power supply there are no oopses any more! So my reported problems with locking are worthless, because it happened with the broken server. -- 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
