* nfsv4 state id errors
@ 2012-08-17 15:57 Richard
2012-08-17 18:18 ` Myklebust, Trond
0 siblings, 1 reply; 8+ messages in thread
From: Richard @ 2012-08-17 15:57 UTC (permalink / raw)
To: linux-nfs
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!
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: nfsv4 state id errors
2012-08-17 15:57 nfsv4 state id errors Richard
@ 2012-08-17 18:18 ` Myklebust, Trond
2012-08-17 18:34 ` Richard
0 siblings, 1 reply; 8+ messages in thread
From: Myklebust, Trond @ 2012-08-17 18:18 UTC (permalink / raw)
To: Richard Smits; +Cc: linux-nfs
T24gRnJpLCAyMDEyLTA4LTE3IGF0IDE3OjU3ICswMjAwLCBSaWNoYXJkIHdyb3RlOg0KPiBIZWxs
bywNCj4gDQo+IEEgY291cGxlIG9mIHdlZWtzIGFnb28gd2UgdXBncmFkZWQgb3VyIE5ldGFwcCBm
aWxlciB0byA4LjEuMVJDMS4gV2UgaGF2ZQ0KPiBhbHdheXMgaGFkIHRyb3VibGUgd2l0aCBORlMg
YW5kIHN0YXRlIGlkJ3MuIFJlc3VsdGluZyBpbiBoYW5naW5nIGNsaWVudHMuDQo+IA0KPiBTb21l
IGJ1Z3Mgd2VyZSBmaXhlZCBpbiA4LjEuMSBidXQgc3RpbGwgdHJvdWJsZS4NCj4gDQo+IE5vdyB3
ZSBoYXZlIHRoZSBmb2xsb3dpbmcgZXJyb3JzIGluIG91ciBjbGllbnQgbWVzc2FnZXMgZmlsZSwg
YWZ0ZXIgYSBoYW5nLg0KPiANCj4gV2hhdCBkb2VzIHRoaXMgOiBORlM6ICJ2NCBzZXJ2ZXIgc3J2
IHJldHVybmVkIGEgYmFkIHNlcXVlbmNlLWlkIGVycm9yISINCj4gbWVhbnMgPw0KDQpDYW4geW91
IHJlbWluZCB1cyB3aGljaCBORlN2NCBjbGllbnRzIHlvdSBhcmUgdXNpbmc/DQoNCkF0IG9uZSBw
b2ludCB0aGUgTkZTdjQgY2xpZW50IHdhcyByZXVzaW5nIG9wZW4gb3duZXJzIGFmdGVyIHRoZXkg
ZmVsbA0Kb3V0IG9mIHRoZSBjbGllbnQgY2FjaGUsIGFuZCB0aGF0IHdvdWxkIGNyZWF0ZSBzeW1w
dG9tcyBzdWNoIGFzIHRoZQ0KYWJvdmUuIFRoYXQgYnVnIGhhcyBzaW5jZSBiZWVuIGZpeGVkIGlu
IHRoZSB1cHN0cmVhbSBrZXJuZWwuDQoNCi0tIA0KVHJvbmQgTXlrbGVidXN0DQpMaW51eCBORlMg
Y2xpZW50IG1haW50YWluZXINCg0KTmV0QXBwDQpUcm9uZC5NeWtsZWJ1c3RAbmV0YXBwLmNvbQ0K
d3d3Lm5ldGFwcC5jb20NCg0K
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: nfsv4 state id errors
2012-08-17 18:18 ` Myklebust, Trond
@ 2012-08-17 18:34 ` Richard
2012-08-17 18:40 ` Myklebust, Trond
0 siblings, 1 reply; 8+ messages in thread
From: Richard @ 2012-08-17 18:34 UTC (permalink / raw)
To: Myklebust, Trond; +Cc: linux-nfs
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.
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: nfsv4 state id errors
2012-08-17 18:34 ` Richard
@ 2012-08-17 18:40 ` Myklebust, Trond
2012-08-17 18:44 ` Richard Smits
0 siblings, 1 reply; 8+ messages in thread
From: Myklebust, Trond @ 2012-08-17 18:40 UTC (permalink / raw)
To: Richard; +Cc: linux-nfs
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=
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: nfsv4 state id errors
2012-08-17 18:40 ` Myklebust, Trond
@ 2012-08-17 18:44 ` Richard Smits
0 siblings, 0 replies; 8+ messages in thread
From: Richard Smits @ 2012-08-17 18:44 UTC (permalink / raw)
To: Myklebust, Trond; +Cc: linux-nfs
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.
>>>
>>
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: nfsv4 state id errors
@ 2012-08-27 10:20 Robbert Eggermont
2012-09-06 7:30 ` Richard Smits
0 siblings, 1 reply; 8+ messages in thread
From: Robbert Eggermont @ 2012-08-27 10:20 UTC (permalink / raw)
To: linux-nfs
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.
(Client: SLED11 SP2, 3.0.34-0.7-default x86_64)
The "hanging" seems to be caused by the server returning an
NFS4ERR_BAD_STATEID(10025) status for PUTFH;LOCK and PUTFH;WRITE;GETATTR
calls. The client is making several hundreds of these identical (same
filehandle) calls each second.
The problem seems to be triggered by (write) actions on an open file
when the Kerberos ticket has expired (especially for .xsession-errors
and files opened by Firefox or Thunderbird).
When (after some time) a new valid ticket is obtained, the kernel
reports this error:
nfs4_reclaim_open_state: unhandled error -10026. Zeroing state
Is this a client or a server problem (and is there by any chance a fix)?
Robbert
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: nfsv4 state id errors
2012-08-27 10:20 Robbert Eggermont
@ 2012-09-06 7:30 ` Richard Smits
0 siblings, 0 replies; 8+ messages in thread
From: Richard Smits @ 2012-09-06 7:30 UTC (permalink / raw)
To: linux-nfs
Anyone any ideas ? Or should we open a case at Netapp ?
Greetings.
On 08/27/2012 12:20 PM, Robbert Eggermont 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.
>
> (Client: SLED11 SP2, 3.0.34-0.7-default x86_64)
>
> The "hanging" seems to be caused by the server returning an
> NFS4ERR_BAD_STATEID(10025) status for PUTFH;LOCK and PUTFH;WRITE;GETATTR
> calls. The client is making several hundreds of these identical (same
> filehandle) calls each second.
>
> The problem seems to be triggered by (write) actions on an open file
> when the Kerberos ticket has expired (especially for .xsession-errors
> and files opened by Firefox or Thunderbird).
>
> When (after some time) a new valid ticket is obtained, the kernel
> reports this error:
> nfs4_reclaim_open_state: unhandled error -10026. Zeroing state
>
> Is this a client or a server problem (and is there by any chance a fix)?
>
> Robbert
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 8+ messages in thread
* nfsv4 state id errors
@ 2012-08-17 15:54 Richard Smits
0 siblings, 0 replies; 8+ messages in thread
From: Richard Smits @ 2012-08-17 15:54 UTC (permalink / raw)
To: linux-nfs
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!
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2012-09-06 7:30 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-08-17 15:57 nfsv4 state id errors Richard
2012-08-17 18:18 ` Myklebust, Trond
2012-08-17 18:34 ` Richard
2012-08-17 18:40 ` Myklebust, Trond
2012-08-17 18:44 ` Richard Smits
-- strict thread matches above, loose matches on Subject: below --
2012-08-27 10:20 Robbert Eggermont
2012-09-06 7:30 ` Richard Smits
2012-08-17 15:54 Richard Smits
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.