NFS mounts not working in ubuntu 16.04?
Before I upgraded to ubuntu 16.04 from 14, I used to be able to mount and access folders on WDMyCloud drives. Now I get the following error:
ls: Cannot open directory '/home/nas/Public': Operation not permitted.
I did not change anything on WDMyCloud.
showmount -e 192.168.0.19 produces:
/nfs *
exports entry on the server:
/nfs *(rw,sync,no_subtree_check,insecure,crossmnt)
user with uid=1000 and gid=1000 on server can access all files. My uid on client is also 1000: id balaji produces this:
uid=1000(balaji) gid=1000(balaji) groups=1000(balaji),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),110(lxd),113(sambashare),119(lpadmin)
fstab entry on client (it is a single line)
192.168.0.19:/nfs /home/nas nfs rw,udp,vers=3,soft,intr,rsize=8192,wsize=8192 0 0
ls /home/nas produces
Public
ls /home/nas/Public
ls: cannot access '/home/nas/Public/': Operation not permitted
I started having this problem after upgrading to ubuntu 16.04. Any suggestions?
16.04 mount nfs
edited Sep 6 '16 at 0:31
steeldriver
68.1k11113184
asked Sep 5 '16 at 23:32
bshyamkumarbshyamkumar
1112
bumped to the homepage by Community♦ 16 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
Before I upgraded to ubuntu 16.04 from 14, I used to be able to mount and access folders on WDMyCloud drives. Now I get the following error:
ls: Cannot open directory '/home/nas/Public': Operation not permitted.
I did not change anything on WDMyCloud.
showmount -e 192.168.0.19 produces:
/nfs *
exports entry on the server:
/nfs *(rw,sync,no_subtree_check,insecure,crossmnt)
user with uid=1000 and gid=1000 on server can access all files. My uid on client is also 1000: id balaji produces this:
uid=1000(balaji) gid=1000(balaji) groups=1000(balaji),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),110(lxd),113(sambashare),119(lpadmin)
fstab entry on client (it is a single line)
192.168.0.19:/nfs /home/nas nfs rw,udp,vers=3,soft,intr,rsize=8192,wsize=8192 0 0
ls /home/nas produces
Public
ls /home/nas/Public
ls: cannot access '/home/nas/Public/': Operation not permitted
I started having this problem after upgrading to ubuntu 16.04. Any suggestions?
16.04 mount nfs
edited Sep 6 '16 at 0:31
steeldriver
68.1k11113184
asked Sep 5 '16 at 23:32
bshyamkumarbshyamkumar
1112
bumped to the homepage by Community♦ 16 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Is/nfs/Publica separate filesystem on the server side (as suggested by thecrossmntoption)? Are you explicitly exporting it?
– steeldriver
Sep 6 '16 at 0:33
Thanks, that fixes it. Looks like something changed on WdMyCloud recently and my upgrade had nothing to do with it breaking.
– bshyamkumar
Sep 6 '16 at 2:04
add a comment |
Before I upgraded to ubuntu 16.04 from 14, I used to be able to mount and access folders on WDMyCloud drives. Now I get the following error:
ls: Cannot open directory '/home/nas/Public': Operation not permitted.
I did not change anything on WDMyCloud.
showmount -e 192.168.0.19 produces:
/nfs *
exports entry on the server:
/nfs *(rw,sync,no_subtree_check,insecure,crossmnt)
user with uid=1000 and gid=1000 on server can access all files. My uid on client is also 1000: id balaji produces this:
uid=1000(balaji) gid=1000(balaji) groups=1000(balaji),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),110(lxd),113(sambashare),119(lpadmin)
fstab entry on client (it is a single line)
192.168.0.19:/nfs /home/nas nfs rw,udp,vers=3,soft,intr,rsize=8192,wsize=8192 0 0
ls /home/nas produces
Public
ls /home/nas/Public
ls: cannot access '/home/nas/Public/': Operation not permitted
I started having this problem after upgrading to ubuntu 16.04. Any suggestions?
16.04 mount nfs
edited Sep 6 '16 at 0:31
steeldriver
68.1k11113184
asked Sep 5 '16 at 23:32
bshyamkumarbshyamkumar
1112
Before I upgraded to ubuntu 16.04 from 14, I used to be able to mount and access folders on WDMyCloud drives. Now I get the following error:
ls: Cannot open directory '/home/nas/Public': Operation not permitted.
I did not change anything on WDMyCloud.
showmount -e 192.168.0.19 produces:
/nfs *
exports entry on the server:
/nfs *(rw,sync,no_subtree_check,insecure,crossmnt)
user with uid=1000 and gid=1000 on server can access all files. My uid on client is also 1000: id balaji produces this:
uid=1000(balaji) gid=1000(balaji) groups=1000(balaji),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),110(lxd),113(sambashare),119(lpadmin)
fstab entry on client (it is a single line)
192.168.0.19:/nfs /home/nas nfs rw,udp,vers=3,soft,intr,rsize=8192,wsize=8192 0 0
ls /home/nas produces
Public
ls /home/nas/Public
ls: cannot access '/home/nas/Public/': Operation not permitted
I started having this problem after upgrading to ubuntu 16.04. Any suggestions?
16.04 mount nfs
16.04 mount nfs
edited Sep 6 '16 at 0:31
steeldriver
68.1k11113184
asked Sep 5 '16 at 23:32
bshyamkumarbshyamkumar
1112
edited Sep 6 '16 at 0:31
steeldriver
68.1k11113184
asked Sep 5 '16 at 23:32
bshyamkumarbshyamkumar
1112
edited Sep 6 '16 at 0:31
steeldriver
68.1k11113184
edited Sep 6 '16 at 0:31
steeldriver
68.1k11113184
edited Sep 6 '16 at 0:31
steeldriver
68.1k11113184
68.1k11113184
asked Sep 5 '16 at 23:32
bshyamkumarbshyamkumar
1112
asked Sep 5 '16 at 23:32
bshyamkumarbshyamkumar
1112
asked Sep 5 '16 at 23:32
bshyamkumarbshyamkumar
1112
1112
bumped to the homepage by Community♦ 16 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 16 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Is/nfs/Publica separate filesystem on the server side (as suggested by thecrossmntoption)? Are you explicitly exporting it?
– steeldriver
Sep 6 '16 at 0:33
Thanks, that fixes it. Looks like something changed on WdMyCloud recently and my upgrade had nothing to do with it breaking.
– bshyamkumar
Sep 6 '16 at 2:04
add a comment |
Is/nfs/Publica separate filesystem on the server side (as suggested by thecrossmntoption)? Are you explicitly exporting it?
– steeldriver
Sep 6 '16 at 0:33
Thanks, that fixes it. Looks like something changed on WdMyCloud recently and my upgrade had nothing to do with it breaking.
– bshyamkumar
Sep 6 '16 at 2:04
Is
/nfs/Public a separate filesystem on the server side (as suggested by the crossmnt option)? Are you explicitly exporting it?– steeldriver
Sep 6 '16 at 0:33
Is
/nfs/Public a separate filesystem on the server side (as suggested by the crossmnt option)? Are you explicitly exporting it?– steeldriver
Sep 6 '16 at 0:33
Thanks, that fixes it. Looks like something changed on WdMyCloud recently and my upgrade had nothing to do with it breaking.
– bshyamkumar
Sep 6 '16 at 2:04
Thanks, that fixes it. Looks like something changed on WdMyCloud recently and my upgrade had nothing to do with it breaking.
– bshyamkumar
Sep 6 '16 at 2:04
add a comment |
1 Answer
1
active
oldest
votes
Each NFS share must be explicitly exported in /etc/exports.
Can also try sudo apt-get install --reinstall nfs-common nfs-utils just in case.
In /etc/fstab, rw,udp,vers=3,soft,intr,rsize=8192,wsize=8192 can be replaced with just auto - over-specifying could sometimes cause some odd issues.
answered Sep 27 '16 at 13:47
EnigmaEnigma
3161418
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2faskubuntu.com%2fquestions%2f821447%2fnfs-mounts-not-working-in-ubuntu-16-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Each NFS share must be explicitly exported in /etc/exports.
Can also try sudo apt-get install --reinstall nfs-common nfs-utils just in case.
In /etc/fstab, rw,udp,vers=3,soft,intr,rsize=8192,wsize=8192 can be replaced with just auto - over-specifying could sometimes cause some odd issues.
answered Sep 27 '16 at 13:47
EnigmaEnigma
3161418
add a comment |
Each NFS share must be explicitly exported in /etc/exports.
Can also try sudo apt-get install --reinstall nfs-common nfs-utils just in case.
In /etc/fstab, rw,udp,vers=3,soft,intr,rsize=8192,wsize=8192 can be replaced with just auto - over-specifying could sometimes cause some odd issues.
answered Sep 27 '16 at 13:47
EnigmaEnigma
3161418
add a comment |
Each NFS share must be explicitly exported in /etc/exports.
Can also try sudo apt-get install --reinstall nfs-common nfs-utils just in case.
In /etc/fstab, rw,udp,vers=3,soft,intr,rsize=8192,wsize=8192 can be replaced with just auto - over-specifying could sometimes cause some odd issues.
answered Sep 27 '16 at 13:47
EnigmaEnigma
3161418
Each NFS share must be explicitly exported in /etc/exports.
Can also try sudo apt-get install --reinstall nfs-common nfs-utils just in case.
In /etc/fstab, rw,udp,vers=3,soft,intr,rsize=8192,wsize=8192 can be replaced with just auto - over-specifying could sometimes cause some odd issues.
answered Sep 27 '16 at 13:47
EnigmaEnigma
3161418
answered Sep 27 '16 at 13:47
EnigmaEnigma
3161418
answered Sep 27 '16 at 13:47
EnigmaEnigma
3161418
answered Sep 27 '16 at 13:47
EnigmaEnigma
3161418
3161418
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f821447%2fnfs-mounts-not-working-in-ubuntu-16-04%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
Is
/nfs/Publica separate filesystem on the server side (as suggested by thecrossmntoption)? Are you explicitly exporting it?– steeldriver
Sep 6 '16 at 0:33
Thanks, that fixes it. Looks like something changed on WdMyCloud recently and my upgrade had nothing to do with it breaking.
– bshyamkumar
Sep 6 '16 at 2:04