Ok, He uses 3.0.34-0.7 Linux 3.0.34-0.7-default #1 SMP Tue Jun 19 09:56:30 UTC 2012 (fbfc70c) x86_64 x86_64 x86_64 GNU/Linux Greetings. On 17-8-2012 20:40, Myklebust, Trond wrote: > Hi, > > OK, but which Linux kernel version is the person using? If you have > access to the machine in question, you can check using the command > 'uname -a'. > > Thanks, > Trond > > On Fri, 2012-08-17 at 20:34 +0200, Richard wrote: >> The person who reported this uses : >> >> nfs-client-1.2.3-18.17.2 >> krb5-1.6.3-133.48.48.1 >> >> I will check next monday with him if this is still the version he uses. >> He uses Suse Linux Enterprise Desktop 11.2. >> >> We use nfs4/krb5 with Windows AD as KDC on a Fas3170. >> >> Greetings. >> >> On 17-8-2012 20:18, Myklebust, Trond wrote: >>> On Fri, 2012-08-17 at 17:57 +0200, Richard wrote: >>>> Hello, >>>> >>>> A couple of weeks agoo we upgraded our Netapp filer to 8.1.1RC1. We have >>>> always had trouble with NFS and state id's. Resulting in hanging clients. >>>> >>>> Some bugs were fixed in 8.1.1 but still trouble. >>>> >>>> Now we have the following errors in our client messages file, after a hang. >>>> >>>> What does this : NFS: "v4 server srv returned a bad sequence-id error!" >>>> means ? >>> >>> Can you remind us which NFSv4 clients you are using? >>> >>> At one point the NFSv4 client was reusing open owners after they fell >>> out of the client cache, and that would create symptoms such as the >>> above. That bug has since been fixed in the upstream kernel. >>> >> > -- 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
