nfsv4 state id errors
Subsystems (2)
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 ?
----
Aug 17 14:08:23 tudxxxxxx kernel: [622014.866818] NFS: v4 server srvxxx returned a bad sequence-id error! Aug 17 14:08:23 tudxxxxxx kernel: [622014.872143] NFS: v4 server returned a bad sequence-id error on an unconfirmed sequence ffff8801112dcc20! Aug 17 14:08:23 tudxxxxxx kernel: [622014.872871] NFS: v4 server returned a bad sequence-id error on an unconfirmed sequence ffff8801112dcc20! Aug 17 14:08:23 tudxxxxxx kernel: [622015.170658] NFS: v4 server returned a bad sequence-id error on an unconfirmed sequence ffff8801112e6820! Aug 17 14:08:23 tudxxxxxx kernel: [622015.278260] NFS: v4 server srvxxx returned a bad sequence-id error! Aug 17 14:08:23 tudxxxxxx kernel: [622015.651868] NFS: v4 server srvxxx returned a bad sequence-id error! Aug 17 14:08:24 tudxxxxxx kernel: [622016.051741] NFS: v4 server srvxxx returned a bad sequence-id error! Aug 17 14:08:25 tudxxxxxx kernel: [622017.155713] NFS: v4 server srvxxx returned a bad sequence-id error! Aug 17 14:08:25 tudxxxxxx kernel: [622017.346225] NFS: v4 server returned a bad sequence-id error on an unconfirmed sequence ffff8800bcf39620! Aug 17 14:08:25 tudxxxxxx kernel: [622017.349781] NFS: v4 server returned a bad sequence-id error on an unconfirmed sequence ffff8800bcf39620! Aug 17 14:08:25 tudxxxxxx kernel: [622017.350840] NFS: v4 server
returned a bad sequence-id error on an unconfirmed sequence ffff8800bcf39620!
T24gRnJpLCAyMDEyLTA4LTE3IGF0IDE3OjU3ICswMjAwLCBSaWNoYXJkIHdyb3RlOg0KPiBIZWxs bywNCj4gDQo+IEEgY291cGxlIG9mIHdlZWtzIGFnb28gd2UgdXBncmFkZWQgb3VyIE5ldGFwcCBm aWxlciB0byA4LjEuMVJDMS4gV2UgaGF2ZQ0KPiBhbHdheXMgaGFkIHRyb3VibGUgd2l0aCBORlMg YW5kIHN0YXRlIGlkJ3MuIFJlc3VsdGluZyBpbiBoYW5naW5nIGNsaWVudHMuDQo+IA0KPiBTb21l IGJ1Z3Mgd2VyZSBmaXhlZCBpbiA4LjEuMSBidXQgc3RpbGwgdHJvdWJsZS4NCj4gDQo+IE5vdyB3 ZSBoYXZlIHRoZSBmb2xsb3dpbmcgZXJyb3JzIGluIG91ciBjbGllbnQgbWVzc2FnZXMgZmlsZSwg YWZ0ZXIgYSBoYW5nLg0KPiANCj4gV2hhdCBkb2VzIHRoaXMgOiBORlM6ICJ2NCBzZXJ2ZXIgc3J2 IHJldHVybmVkIGEgYmFkIHNlcXVlbmNlLWlkIGVycm9yISINCj4gbWVhbnMgPw0KDQpDYW4geW91 IHJlbWluZCB1cyB3aGljaCBORlN2NCBjbGllbnRzIHlvdSBhcmUgdXNpbmc/DQoNCkF0IG9uZSBw b2ludCB0aGUgTkZTdjQgY2xpZW50IHdhcyByZXVzaW5nIG9wZW4gb3duZXJzIGFmdGVyIHRoZXkg ZmVsbA0Kb3V0IG9mIHRoZSBjbGllbnQgY2FjaGUsIGFuZCB0aGF0IHdvdWxkIGNyZWF0ZSBzeW1w dG9tcyBzdWNoIGFzIHRoZQ0KYWJvdmUuIFRoYXQgYnVnIGhhcyBzaW5jZSBiZWVuIGZpeGVkIGlu IHRoZSB1cHN0cmVhbSBrZXJuZWwuDQoNCi0tIA0KVHJvbmQgTXlrbGVidXN0DQpMaW51eCBORlMg Y2xpZW50IG1haW50YWluZXINCg0KTmV0QXBwDQpUcm9uZC5NeWtsZWJ1c3RAbmV0YXBwLmNvbQ0K d3d3Lm5ldGFwcC5jb20NCg0K
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.
Quoted 19 lines · Trond
Quoted 11 lines · Richard
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.
SGksDQoNCk9LLCBidXQgd2hpY2ggTGludXgga2VybmVsIHZlcnNpb24gaXMgdGhlIHBlcnNvbiB1 c2luZz8gSWYgeW91IGhhdmUNCmFjY2VzcyB0byB0aGUgbWFjaGluZSBpbiBxdWVzdGlvbiwgeW91 IGNhbiBjaGVjayB1c2luZyB0aGUgY29tbWFuZA0KJ3VuYW1lIC1hJy4NCg0KVGhhbmtzLA0KICBU cm9uZA0KDQpPbiBGcmksIDIwMTItMDgtMTcgYXQgMjA6MzQgKzAyMDAsIFJpY2hhcmQgd3JvdGU6 DQo+IFRoZSBwZXJzb24gd2hvIHJlcG9ydGVkIHRoaXMgdXNlcyA6DQo+IA0KPiBuZnMtY2xpZW50 LTEuMi4zLTE4LjE3LjINCj4ga3JiNS0xLjYuMy0xMzMuNDguNDguMQ0KPiANCj4gSSB3aWxsIGNo ZWNrIG5leHQgbW9uZGF5IHdpdGggaGltIGlmIHRoaXMgaXMgc3RpbGwgdGhlIHZlcnNpb24gaGUg dXNlcy4NCj4gSGUgdXNlcyBTdXNlIExpbnV4IEVudGVycHJpc2UgRGVza3RvcCAxMS4yLg0KPiAN Cj4gV2UgdXNlIG5mczQva3JiNSB3aXRoIFdpbmRvd3MgQUQgYXMgS0RDIG9uIGEgRmFzMzE3MC4N Cj4gDQo+IEdyZWV0aW5ncy4NCj4gDQo+IE9uIDE3LTgtMjAxMiAyMDoxOCwgTXlrbGVidXN0LCBU cm9uZCB3cm90ZToNCj4gPiBPbiBGcmksIDIwMTItMDgtMTcgYXQgMTc6NTcgKzAyMDAsIFJpY2hh cmQgd3JvdGU6DQo+ID4+IEhlbGxvLA0KPiA+Pg0KPiA+PiBBIGNvdXBsZSBvZiB3ZWVrcyBhZ29v IHdlIHVwZ3JhZGVkIG91ciBOZXRhcHAgZmlsZXIgdG8gOC4xLjFSQzEuIFdlIGhhdmUNCj4gPj4g YWx3YXlzIGhhZCB0cm91YmxlIHdpdGggTkZTIGFuZCBzdGF0ZSBpZCdzLiBSZXN1bHRpbmcgaW4g aGFuZ2luZyBjbGllbnRzLg0KPiA+Pg0KPiA+PiBTb21lIGJ1Z3Mgd2VyZSBmaXhlZCBpbiA4LjEu MSBidXQgc3RpbGwgdHJvdWJsZS4NCj4gPj4NCj4gPj4gTm93IHdlIGhhdmUgdGhlIGZvbGxvd2lu ZyBlcnJvcnMgaW4gb3VyIGNsaWVudCBtZXNzYWdlcyBmaWxlLCBhZnRlciBhIGhhbmcuDQo+ID4+ DQo+ID4+IFdoYXQgZG9lcyB0aGlzIDogTkZTOiAidjQgc2VydmVyIHNydiByZXR1cm5lZCBhIGJh ZCBzZXF1ZW5jZS1pZCBlcnJvciEiDQo+ID4+IG1lYW5zID8NCj4gPiANCj4gPiBDYW4geW91IHJl bWluZCB1cyB3aGljaCBORlN2NCBjbGllbnRzIHlvdSBhcmUgdXNpbmc/DQo+ID4gDQo+ID4gQXQg b25lIHBvaW50IHRoZSBORlN2NCBjbGllbnQgd2FzIHJldXNpbmcgb3BlbiBvd25lcnMgYWZ0ZXIg dGhleSBmZWxsDQo+ID4gb3V0IG9mIHRoZSBjbGllbnQgY2FjaGUsIGFuZCB0aGF0IHdvdWxkIGNy ZWF0ZSBzeW1wdG9tcyBzdWNoIGFzIHRoZQ0KPiA+IGFib3ZlLiBUaGF0IGJ1ZyBoYXMgc2luY2Ug YmVlbiBmaXhlZCBpbiB0aGUgdXBzdHJlYW0ga2VybmVsLg0KPiA+IA0KPiANCg0KLS0gDQpUcm9u ZCBNeWtsZWJ1c3QNCkxpbnV4IE5GUyBjbGllbnQgbWFpbnRhaW5lcg0KDQpOZXRBcHANClRyb25k Lk15a2xlYnVzdEBuZXRhcHAuY29tDQp3d3cubmV0YXBwLmNvbQ0KDQo=
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.
Quoted 44 lines · Trond
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,
TrondQuoted 33 lines · Richard
The person who reported this uses :
nfs-client-1.2.3-18.17.2
krb5-1.6.3-133.48.48.1I 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.
Quoted 19 lines · Trond
Quoted 11 lines · Richard
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.