NFSv4 Errors, But Not in NFSv3NFSv3 with Kerberos “unmatched host” errorStop broken NFS mounts from...
How do native German speakers usually express skepticism (using even) about a premise?
Why did Old English lose both thorn and eth?
Debian testing - upgrade "Buster" to "Bullseye" version, no server for security.debian.org
What are some further readings in Econometrics you recommend?
Integer Lists of Noah
Write a function
The joke office
Would a carnivorous diet be able to support a giant worm?
Addressing unnecessary daily meetings with manager?
Is it possible to split a vertex?
Matrix with arrows and comments
What happens to unproductive professors?
How to design a CMC (Common Mode Choke) footprint to allow no-pop solution
In Spider-Man: Far From Home, is this superhero name a reference to another comic book?
Why is the ladder of the LM always in the dark side of the LM?
How effective would wooden scale armor be in a medieval setting?
WTB Horizon 47c - small crack in the middle of the tire
Chrysanthemum bejeweled with dew drops
Given a 32 bit number, what is an efficient way to scale each byte by a certain factor?
Graduate student with abysmal English writing skills, how to help
Party going through airport security at separate times?
What is the right approach to quit a job during probation period for a competing offer?
When an electron changes its spin, or any other intrinsic property, is it still the same electron?
LED glows slightly during soldering
NFSv4 Errors, But Not in NFSv3
NFSv3 with Kerberos “unmatched host” errorStop broken NFS mounts from locking a directory?Disable NFSv4 (server) on Debian, allow NFSv3RPC Authentication Error when mounting NFSNFSv3 works but not NFSv4 on ArmbianWhy do I get “no credentials cache” error when mounting Kerberized NFS share?WD MyCloud NFS Mount to Asus Merlin Router: NFS mount troubleshooting: “no such device”Stale NFS File Handle why does fsid resolve it?Problem with NFS mount when FS is shared for all clients however works when a specific client network is specifiedFreeIPA Kerberized NFSv4 Group Membership Issue
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I'm working on an NFS solution for RHEL6.5 clients (all VMs) with RHEL6.5 and RHEL7 hosts. Currently, the RHEL7 host with RHEL6.5 clients works fine. The trouble is with the RHEL6.5 host.
These problems might be down to aspects of the server I can't control, as the server has been having issues lately that it didn't last year. If you think that's the issue, please suggest ways I can prove this to my superiors, and begin the process of getting a new machine.
The solution was initially being crafted to use NFSv4, which was going swell. The RHEL6.5 host, however, is not as keen as the RHEL7 host. Mounts succeed, but file access does not work, e.g. cp, less. In terminal, they hang. tail-ing the client's /var/log/messages shows state manager: lease expired failed on NFSv4 server nfs_master with error 10018. Per the standard, that error code is for NFS4ERR_RESOURCE, documented here. My attempt to resolve the resource issue was by increasing the number of nfsd processes via the command-line, and by setting the appropriate config in /etc/sysconfig/nfs. It didn't help. This issue also occurs if the exported directory is mounted on the NFS server itself.
What is not shown in the logs for the host nor client is another error 10022, or at least I assume this is an NFSv4 error code. This is only viewable when tcpdump-ing the interface that the NFS communication is going over: IP test-host.nfs > test_client-1.3297002672: reply ok 52 getattr ERROR: unk 10022 If this error code is indeed an NFSv4 one, then it is for NFS4ERR_STALE_CLIENTID documented here.
When the mount command is changed to set nfsvers=3, actions like cp are successful and generate no errors on the client nor the host. The first attempt will take a little long, 5 seconds maybe, then futures actions are much faster.
At a time there will be at most four clients mounting the export and reading from it, and potentially the same file.
So, my questions are:
- What are the server-side resources being referred to by the
NFS4ERR_RESOURCEdescription? - How do I resolve
NFS4ERR_RESOURCEandNFS4ERR_STALE_CLIENTIDerrors? - Why is NFSv3 functioning as expected, but not NFSv4?
nfs-utils version and release (for both clients and RHEL6.5 host): 1.2.3.39.el6
mount commands:
mount -n -t nfs -o ro,noexec,timeo=10,retrans=3,retry=0,soft,rsize=32768,intr,noatimemount -n -t nfs -o nfsvers=3,ro,noexec,timeo=10,retrans=3,retry=0,soft,rsize=32768,intr,noatime
rhel mount nfs onc-rpc
asked 2 hours ago
UngeheuerUngeheuer
1428 bronze badges
add a comment |
I'm working on an NFS solution for RHEL6.5 clients (all VMs) with RHEL6.5 and RHEL7 hosts. Currently, the RHEL7 host with RHEL6.5 clients works fine. The trouble is with the RHEL6.5 host.
These problems might be down to aspects of the server I can't control, as the server has been having issues lately that it didn't last year. If you think that's the issue, please suggest ways I can prove this to my superiors, and begin the process of getting a new machine.
The solution was initially being crafted to use NFSv4, which was going swell. The RHEL6.5 host, however, is not as keen as the RHEL7 host. Mounts succeed, but file access does not work, e.g. cp, less. In terminal, they hang. tail-ing the client's /var/log/messages shows state manager: lease expired failed on NFSv4 server nfs_master with error 10018. Per the standard, that error code is for NFS4ERR_RESOURCE, documented here. My attempt to resolve the resource issue was by increasing the number of nfsd processes via the command-line, and by setting the appropriate config in /etc/sysconfig/nfs. It didn't help. This issue also occurs if the exported directory is mounted on the NFS server itself.
What is not shown in the logs for the host nor client is another error 10022, or at least I assume this is an NFSv4 error code. This is only viewable when tcpdump-ing the interface that the NFS communication is going over: IP test-host.nfs > test_client-1.3297002672: reply ok 52 getattr ERROR: unk 10022 If this error code is indeed an NFSv4 one, then it is for NFS4ERR_STALE_CLIENTID documented here.
When the mount command is changed to set nfsvers=3, actions like cp are successful and generate no errors on the client nor the host. The first attempt will take a little long, 5 seconds maybe, then futures actions are much faster.
At a time there will be at most four clients mounting the export and reading from it, and potentially the same file.
So, my questions are:
- What are the server-side resources being referred to by the
NFS4ERR_RESOURCEdescription? - How do I resolve
NFS4ERR_RESOURCEandNFS4ERR_STALE_CLIENTIDerrors? - Why is NFSv3 functioning as expected, but not NFSv4?
nfs-utils version and release (for both clients and RHEL6.5 host): 1.2.3.39.el6
mount commands:
mount -n -t nfs -o ro,noexec,timeo=10,retrans=3,retry=0,soft,rsize=32768,intr,noatimemount -n -t nfs -o nfsvers=3,ro,noexec,timeo=10,retrans=3,retry=0,soft,rsize=32768,intr,noatime
rhel mount nfs onc-rpc
asked 2 hours ago
UngeheuerUngeheuer
1428 bronze badges
You might want to try to force it to use TCP only. Or UDP only. I forget off-hand which, but that helped me in the past when I had problems with C6 <=> C7.
– Aaron D. Marasco
1 hour ago
add a comment |
I'm working on an NFS solution for RHEL6.5 clients (all VMs) with RHEL6.5 and RHEL7 hosts. Currently, the RHEL7 host with RHEL6.5 clients works fine. The trouble is with the RHEL6.5 host.
These problems might be down to aspects of the server I can't control, as the server has been having issues lately that it didn't last year. If you think that's the issue, please suggest ways I can prove this to my superiors, and begin the process of getting a new machine.
The solution was initially being crafted to use NFSv4, which was going swell. The RHEL6.5 host, however, is not as keen as the RHEL7 host. Mounts succeed, but file access does not work, e.g. cp, less. In terminal, they hang. tail-ing the client's /var/log/messages shows state manager: lease expired failed on NFSv4 server nfs_master with error 10018. Per the standard, that error code is for NFS4ERR_RESOURCE, documented here. My attempt to resolve the resource issue was by increasing the number of nfsd processes via the command-line, and by setting the appropriate config in /etc/sysconfig/nfs. It didn't help. This issue also occurs if the exported directory is mounted on the NFS server itself.
What is not shown in the logs for the host nor client is another error 10022, or at least I assume this is an NFSv4 error code. This is only viewable when tcpdump-ing the interface that the NFS communication is going over: IP test-host.nfs > test_client-1.3297002672: reply ok 52 getattr ERROR: unk 10022 If this error code is indeed an NFSv4 one, then it is for NFS4ERR_STALE_CLIENTID documented here.
When the mount command is changed to set nfsvers=3, actions like cp are successful and generate no errors on the client nor the host. The first attempt will take a little long, 5 seconds maybe, then futures actions are much faster.
At a time there will be at most four clients mounting the export and reading from it, and potentially the same file.
So, my questions are:
- What are the server-side resources being referred to by the
NFS4ERR_RESOURCEdescription? - How do I resolve
NFS4ERR_RESOURCEandNFS4ERR_STALE_CLIENTIDerrors? - Why is NFSv3 functioning as expected, but not NFSv4?
nfs-utils version and release (for both clients and RHEL6.5 host): 1.2.3.39.el6
mount commands:
mount -n -t nfs -o ro,noexec,timeo=10,retrans=3,retry=0,soft,rsize=32768,intr,noatimemount -n -t nfs -o nfsvers=3,ro,noexec,timeo=10,retrans=3,retry=0,soft,rsize=32768,intr,noatime
rhel mount nfs onc-rpc
asked 2 hours ago
UngeheuerUngeheuer
1428 bronze badges
I'm working on an NFS solution for RHEL6.5 clients (all VMs) with RHEL6.5 and RHEL7 hosts. Currently, the RHEL7 host with RHEL6.5 clients works fine. The trouble is with the RHEL6.5 host.
These problems might be down to aspects of the server I can't control, as the server has been having issues lately that it didn't last year. If you think that's the issue, please suggest ways I can prove this to my superiors, and begin the process of getting a new machine.
The solution was initially being crafted to use NFSv4, which was going swell. The RHEL6.5 host, however, is not as keen as the RHEL7 host. Mounts succeed, but file access does not work, e.g. cp, less. In terminal, they hang. tail-ing the client's /var/log/messages shows state manager: lease expired failed on NFSv4 server nfs_master with error 10018. Per the standard, that error code is for NFS4ERR_RESOURCE, documented here. My attempt to resolve the resource issue was by increasing the number of nfsd processes via the command-line, and by setting the appropriate config in /etc/sysconfig/nfs. It didn't help. This issue also occurs if the exported directory is mounted on the NFS server itself.
What is not shown in the logs for the host nor client is another error 10022, or at least I assume this is an NFSv4 error code. This is only viewable when tcpdump-ing the interface that the NFS communication is going over: IP test-host.nfs > test_client-1.3297002672: reply ok 52 getattr ERROR: unk 10022 If this error code is indeed an NFSv4 one, then it is for NFS4ERR_STALE_CLIENTID documented here.
When the mount command is changed to set nfsvers=3, actions like cp are successful and generate no errors on the client nor the host. The first attempt will take a little long, 5 seconds maybe, then futures actions are much faster.
At a time there will be at most four clients mounting the export and reading from it, and potentially the same file.
So, my questions are:
- What are the server-side resources being referred to by the
NFS4ERR_RESOURCEdescription? - How do I resolve
NFS4ERR_RESOURCEandNFS4ERR_STALE_CLIENTIDerrors? - Why is NFSv3 functioning as expected, but not NFSv4?
nfs-utils version and release (for both clients and RHEL6.5 host): 1.2.3.39.el6
mount commands:
mount -n -t nfs -o ro,noexec,timeo=10,retrans=3,retry=0,soft,rsize=32768,intr,noatimemount -n -t nfs -o nfsvers=3,ro,noexec,timeo=10,retrans=3,retry=0,soft,rsize=32768,intr,noatime
rhel mount nfs onc-rpc
rhel mount nfs onc-rpc
asked 2 hours ago
UngeheuerUngeheuer
1428 bronze badges
asked 2 hours ago
UngeheuerUngeheuer
1428 bronze badges
asked 2 hours ago
UngeheuerUngeheuer
1428 bronze badges
asked 2 hours ago
UngeheuerUngeheuer
1428 bronze badges
asked 2 hours ago
UngeheuerUngeheuer
1428 bronze badges
1428 bronze badges
You might want to try to force it to use TCP only. Or UDP only. I forget off-hand which, but that helped me in the past when I had problems with C6 <=> C7.
– Aaron D. Marasco
1 hour ago
add a comment |
You might want to try to force it to use TCP only. Or UDP only. I forget off-hand which, but that helped me in the past when I had problems with C6 <=> C7.
– Aaron D. Marasco
1 hour ago
You might want to try to force it to use TCP only. Or UDP only. I forget off-hand which, but that helped me in the past when I had problems with C6 <=> C7.
– Aaron D. Marasco
1 hour ago
You might want to try to force it to use TCP only. Or UDP only. I forget off-hand which, but that helped me in the past when I had problems with C6 <=> C7.
– Aaron D. Marasco
1 hour ago
add a comment |
0
active
oldest
votes
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%2f529053%2fnfsv4-errors-but-not-in-nfsv3%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f529053%2fnfsv4-errors-but-not-in-nfsv3%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
You might want to try to force it to use TCP only. Or UDP only. I forget off-hand which, but that helped me in the past when I had problems with C6 <=> C7.
– Aaron D. Marasco
1 hour ago