nfsstat -s: What does sequence mean?
I am having a lot of trouble with my NFS v4 server running over infiniband (IPoIB), every time the load gets high, the nfs server locks up and I have to reboot the server to fix the problem. I get the following messages every few seconds:
Message from syslogd@fruster at Jul 14 12:51:54 ...
kernel:BUG: soft lockup - CPU#6 stuck for 22s! [nfsd:15806]
I have been trying to debug this and figure out what is going on, and so I checked nfsstat -s
to see what was using all of the bandwidth:
Server rpc stats:
calls badcalls badclnt badauth xdrcall
241998732 0 0 0 0
Server nfs v4:
null compound
3 0% 242004087 99%
Server nfs v4 operations:
op0-unused op1-unused op2-future access close commit
0 0% 0 0% 0 0% 148697 0% 65006 0% 124611 0%
create delegpurge delegreturn getattr getfh link
3072 0% 0 0% 10373 0% 6028483 2% 120565 0% 0 0%
lock lockt locku lookup lookup_root nverify
0 0% 0 0% 0 0% 52306 0% 0 0% 0 0%
open openattr open_conf open_dgrd putfh putpubfh
90478 0% 0 0% 223 0% 18760 0% 18834351 6% 0 0%
putrootfh read readdir readlink remove rename
65 0% 12579510 4% 4540 0% 5 0% 24848 0% 20232 0%
renew restorefh savefh secinfo setattr setcltid
23413 0% 0 0% 20241 0% 0 0% 1073 0% 66 0%
setcltidconf verify write rellockowner bc_ctl bind_conn
66 0% 0 0% 5716220 2% 0 0% 0 0% 13 0%
exchange_id create_ses destroy_ses free_stateid getdirdeleg getdevinfo
101 0% 159 0% 58 0% 0 0% 0 0% 0 0%
getdevlist layoutcommit layoutget layoutreturn secinfononam sequence
0 0% 0 0% 0 0% 0 0% 0 0% 225439523 83%
set_ssv test_stateid want_deleg destroy_clid reclaim_comp
0 0% 0 0% 0 0% 0 0% 55 0%
As you can see, 'sequence' is using 83% of the NFS bandwidth, but I have no idea what 'sequence' is, and I can't find it online anywhere because when I search for 'nfsstat -s output sequence' I get a bunch of pages telling me to 'do the following steps in sequence'.
Does anyone have any idea what 'sequence' is? Bonus points if you have a suggestion as to why NFS is freezing up.
Thanks
centos nfs
add a comment |
I am having a lot of trouble with my NFS v4 server running over infiniband (IPoIB), every time the load gets high, the nfs server locks up and I have to reboot the server to fix the problem. I get the following messages every few seconds:
Message from syslogd@fruster at Jul 14 12:51:54 ...
kernel:BUG: soft lockup - CPU#6 stuck for 22s! [nfsd:15806]
I have been trying to debug this and figure out what is going on, and so I checked nfsstat -s
to see what was using all of the bandwidth:
Server rpc stats:
calls badcalls badclnt badauth xdrcall
241998732 0 0 0 0
Server nfs v4:
null compound
3 0% 242004087 99%
Server nfs v4 operations:
op0-unused op1-unused op2-future access close commit
0 0% 0 0% 0 0% 148697 0% 65006 0% 124611 0%
create delegpurge delegreturn getattr getfh link
3072 0% 0 0% 10373 0% 6028483 2% 120565 0% 0 0%
lock lockt locku lookup lookup_root nverify
0 0% 0 0% 0 0% 52306 0% 0 0% 0 0%
open openattr open_conf open_dgrd putfh putpubfh
90478 0% 0 0% 223 0% 18760 0% 18834351 6% 0 0%
putrootfh read readdir readlink remove rename
65 0% 12579510 4% 4540 0% 5 0% 24848 0% 20232 0%
renew restorefh savefh secinfo setattr setcltid
23413 0% 0 0% 20241 0% 0 0% 1073 0% 66 0%
setcltidconf verify write rellockowner bc_ctl bind_conn
66 0% 0 0% 5716220 2% 0 0% 0 0% 13 0%
exchange_id create_ses destroy_ses free_stateid getdirdeleg getdevinfo
101 0% 159 0% 58 0% 0 0% 0 0% 0 0%
getdevlist layoutcommit layoutget layoutreturn secinfononam sequence
0 0% 0 0% 0 0% 0 0% 0 0% 225439523 83%
set_ssv test_stateid want_deleg destroy_clid reclaim_comp
0 0% 0 0% 0 0% 0 0% 55 0%
As you can see, 'sequence' is using 83% of the NFS bandwidth, but I have no idea what 'sequence' is, and I can't find it online anywhere because when I search for 'nfsstat -s output sequence' I get a bunch of pages telling me to 'do the following steps in sequence'.
Does anyone have any idea what 'sequence' is? Bonus points if you have a suggestion as to why NFS is freezing up.
Thanks
centos nfs
add a comment |
I am having a lot of trouble with my NFS v4 server running over infiniband (IPoIB), every time the load gets high, the nfs server locks up and I have to reboot the server to fix the problem. I get the following messages every few seconds:
Message from syslogd@fruster at Jul 14 12:51:54 ...
kernel:BUG: soft lockup - CPU#6 stuck for 22s! [nfsd:15806]
I have been trying to debug this and figure out what is going on, and so I checked nfsstat -s
to see what was using all of the bandwidth:
Server rpc stats:
calls badcalls badclnt badauth xdrcall
241998732 0 0 0 0
Server nfs v4:
null compound
3 0% 242004087 99%
Server nfs v4 operations:
op0-unused op1-unused op2-future access close commit
0 0% 0 0% 0 0% 148697 0% 65006 0% 124611 0%
create delegpurge delegreturn getattr getfh link
3072 0% 0 0% 10373 0% 6028483 2% 120565 0% 0 0%
lock lockt locku lookup lookup_root nverify
0 0% 0 0% 0 0% 52306 0% 0 0% 0 0%
open openattr open_conf open_dgrd putfh putpubfh
90478 0% 0 0% 223 0% 18760 0% 18834351 6% 0 0%
putrootfh read readdir readlink remove rename
65 0% 12579510 4% 4540 0% 5 0% 24848 0% 20232 0%
renew restorefh savefh secinfo setattr setcltid
23413 0% 0 0% 20241 0% 0 0% 1073 0% 66 0%
setcltidconf verify write rellockowner bc_ctl bind_conn
66 0% 0 0% 5716220 2% 0 0% 0 0% 13 0%
exchange_id create_ses destroy_ses free_stateid getdirdeleg getdevinfo
101 0% 159 0% 58 0% 0 0% 0 0% 0 0%
getdevlist layoutcommit layoutget layoutreturn secinfononam sequence
0 0% 0 0% 0 0% 0 0% 0 0% 225439523 83%
set_ssv test_stateid want_deleg destroy_clid reclaim_comp
0 0% 0 0% 0 0% 0 0% 55 0%
As you can see, 'sequence' is using 83% of the NFS bandwidth, but I have no idea what 'sequence' is, and I can't find it online anywhere because when I search for 'nfsstat -s output sequence' I get a bunch of pages telling me to 'do the following steps in sequence'.
Does anyone have any idea what 'sequence' is? Bonus points if you have a suggestion as to why NFS is freezing up.
Thanks
centos nfs
I am having a lot of trouble with my NFS v4 server running over infiniband (IPoIB), every time the load gets high, the nfs server locks up and I have to reboot the server to fix the problem. I get the following messages every few seconds:
Message from syslogd@fruster at Jul 14 12:51:54 ...
kernel:BUG: soft lockup - CPU#6 stuck for 22s! [nfsd:15806]
I have been trying to debug this and figure out what is going on, and so I checked nfsstat -s
to see what was using all of the bandwidth:
Server rpc stats:
calls badcalls badclnt badauth xdrcall
241998732 0 0 0 0
Server nfs v4:
null compound
3 0% 242004087 99%
Server nfs v4 operations:
op0-unused op1-unused op2-future access close commit
0 0% 0 0% 0 0% 148697 0% 65006 0% 124611 0%
create delegpurge delegreturn getattr getfh link
3072 0% 0 0% 10373 0% 6028483 2% 120565 0% 0 0%
lock lockt locku lookup lookup_root nverify
0 0% 0 0% 0 0% 52306 0% 0 0% 0 0%
open openattr open_conf open_dgrd putfh putpubfh
90478 0% 0 0% 223 0% 18760 0% 18834351 6% 0 0%
putrootfh read readdir readlink remove rename
65 0% 12579510 4% 4540 0% 5 0% 24848 0% 20232 0%
renew restorefh savefh secinfo setattr setcltid
23413 0% 0 0% 20241 0% 0 0% 1073 0% 66 0%
setcltidconf verify write rellockowner bc_ctl bind_conn
66 0% 0 0% 5716220 2% 0 0% 0 0% 13 0%
exchange_id create_ses destroy_ses free_stateid getdirdeleg getdevinfo
101 0% 159 0% 58 0% 0 0% 0 0% 0 0%
getdevlist layoutcommit layoutget layoutreturn secinfononam sequence
0 0% 0 0% 0 0% 0 0% 0 0% 225439523 83%
set_ssv test_stateid want_deleg destroy_clid reclaim_comp
0 0% 0 0% 0 0% 0 0% 55 0%
As you can see, 'sequence' is using 83% of the NFS bandwidth, but I have no idea what 'sequence' is, and I can't find it online anywhere because when I search for 'nfsstat -s output sequence' I get a bunch of pages telling me to 'do the following steps in sequence'.
Does anyone have any idea what 'sequence' is? Bonus points if you have a suggestion as to why NFS is freezing up.
Thanks
centos nfs
centos nfs
asked Jul 14 '15 at 19:56
Mike DacreMike Dacre
1184
1184
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Definition appears to be as below.
RFC 3530 NFS v4 : Network File System (NFS) version 4 Protocol
NFS4ERR_BAD_SEQID
The sequence number in a locking request is neither the next expected number or the last number processed.
The source for nfsstat didn't reveal any more info unfortunately.
UPDATE 15th July : Possibility of Bug 651409 - BAD SEQID error messages returned by the NFS server being the culprit here.
1
Thanks @steve, thats great. Now I just need to figure out why I am getting so many out of sequence locking requests.
– Mike Dacre
Jul 14 '15 at 22:27
add a comment |
This is Operation 53 of NFSv4.1
The SEQUENCE operation is used by the server to implement session
request control and the reply cache semantics.
Source
The operation itself doesn't seem to indicate any error or problem.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f216004%2fnfsstat-s-what-does-sequence-mean%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Definition appears to be as below.
RFC 3530 NFS v4 : Network File System (NFS) version 4 Protocol
NFS4ERR_BAD_SEQID
The sequence number in a locking request is neither the next expected number or the last number processed.
The source for nfsstat didn't reveal any more info unfortunately.
UPDATE 15th July : Possibility of Bug 651409 - BAD SEQID error messages returned by the NFS server being the culprit here.
1
Thanks @steve, thats great. Now I just need to figure out why I am getting so many out of sequence locking requests.
– Mike Dacre
Jul 14 '15 at 22:27
add a comment |
Definition appears to be as below.
RFC 3530 NFS v4 : Network File System (NFS) version 4 Protocol
NFS4ERR_BAD_SEQID
The sequence number in a locking request is neither the next expected number or the last number processed.
The source for nfsstat didn't reveal any more info unfortunately.
UPDATE 15th July : Possibility of Bug 651409 - BAD SEQID error messages returned by the NFS server being the culprit here.
1
Thanks @steve, thats great. Now I just need to figure out why I am getting so many out of sequence locking requests.
– Mike Dacre
Jul 14 '15 at 22:27
add a comment |
Definition appears to be as below.
RFC 3530 NFS v4 : Network File System (NFS) version 4 Protocol
NFS4ERR_BAD_SEQID
The sequence number in a locking request is neither the next expected number or the last number processed.
The source for nfsstat didn't reveal any more info unfortunately.
UPDATE 15th July : Possibility of Bug 651409 - BAD SEQID error messages returned by the NFS server being the culprit here.
Definition appears to be as below.
RFC 3530 NFS v4 : Network File System (NFS) version 4 Protocol
NFS4ERR_BAD_SEQID
The sequence number in a locking request is neither the next expected number or the last number processed.
The source for nfsstat didn't reveal any more info unfortunately.
UPDATE 15th July : Possibility of Bug 651409 - BAD SEQID error messages returned by the NFS server being the culprit here.
edited Jul 15 '15 at 21:29
answered Jul 14 '15 at 21:07
stevesteve
14.1k22552
14.1k22552
1
Thanks @steve, thats great. Now I just need to figure out why I am getting so many out of sequence locking requests.
– Mike Dacre
Jul 14 '15 at 22:27
add a comment |
1
Thanks @steve, thats great. Now I just need to figure out why I am getting so many out of sequence locking requests.
– Mike Dacre
Jul 14 '15 at 22:27
1
1
Thanks @steve, thats great. Now I just need to figure out why I am getting so many out of sequence locking requests.
– Mike Dacre
Jul 14 '15 at 22:27
Thanks @steve, thats great. Now I just need to figure out why I am getting so many out of sequence locking requests.
– Mike Dacre
Jul 14 '15 at 22:27
add a comment |
This is Operation 53 of NFSv4.1
The SEQUENCE operation is used by the server to implement session
request control and the reply cache semantics.
Source
The operation itself doesn't seem to indicate any error or problem.
add a comment |
This is Operation 53 of NFSv4.1
The SEQUENCE operation is used by the server to implement session
request control and the reply cache semantics.
Source
The operation itself doesn't seem to indicate any error or problem.
add a comment |
This is Operation 53 of NFSv4.1
The SEQUENCE operation is used by the server to implement session
request control and the reply cache semantics.
Source
The operation itself doesn't seem to indicate any error or problem.
This is Operation 53 of NFSv4.1
The SEQUENCE operation is used by the server to implement session
request control and the reply cache semantics.
Source
The operation itself doesn't seem to indicate any error or problem.
answered Feb 17 at 16:08
isarandiisarandi
1242
1242
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f216004%2fnfsstat-s-what-does-sequence-mean%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown