Linux

48069 readers

811 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

nooter692@lemmy.ml

AgreeableLandscape@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

NFS: permission denied even locally (lemmy.world)

submitted 6 months ago by peregus@lemmy.world to c/linux@lemmy.ml

5 comments fedilink hide all child comments

Hi all, I don't know if this is the right place to post this...let me know :)

I'm trying to create a NFS share, this is my /etc/exports:

/mnt/pool/var_VM_docker/ 172.31.0.0/24(rw,sync,no_subtree_check)

When I try to connect with:

sudo mount -t nfs -o nfsvers=3 -vvvv 172.31.0.1:/mnt/pool/var_VM_docker /mnt/test

I get:

mount.nfs: timeout set for Mon Apr 15 19:07:11 2024
mount.nfs: trying text-based options 'nfsvers=3,addr=172.31.0.1'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 172.31.0.1 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 172.31.0.1 prog 100005 vers 3 prot UDP port 41067
mount.nfs: mount(2): Permission denied
mount.nfs: access denied by server while mounting 172.31.0.1:/mnt/pool/var_VM_docker

I don't have iptables enabled, nor SELinux. I've tried exporting it on 127.0.0.1 and connecting it to 127.0.0.1, but the problem persist. What am I doing wrong?

top 5 comments

sorted by: hot top controversial new old

[–] lemmyreader@lemmy.ml 5 points 6 months ago (1 children)

Did you have NFS working before ? For NFS version 3 and below you will need to have rpcbind running, and years ago that changed the default to listening on 127.0.0.1 on some Linux distributions. Here's a quick search result for NFS4 : https://www.suse.com/support/kb/doc/?id=000019530 And from the best Linux wiki of late : https://wiki.archlinux.org/title/NFS

[–] peregus@lemmy.world 2 points 6 months ago

No, I've never used NFS. I've solved with this export:

/mnt/pool/vm_docker/ 172.31.0.0/24(rw,fsid=1,sync,no_root_squash,no_subtree_check)

And this mount:

sudo mount -t nfs -o vers=3 172.31.0.1:/mnt/pool/vm_docker /mnt/nfs/

Made it permanent with this /etc/fstab:

172.31.0.1:/mnt/pool/vm_docker /mnt/nfs nfs vers=3,rw 0 0

[–] theit8514@lemmy.world 4 points 6 months ago

As an aside, these are the client logs, check the /var/log/ auth.log or secure files or journalctl to see if the server logged why the access was denied.

[–] krolden@lemmy.ml 2 points 6 months ago

Try mounting it without the mount options. Also why -vvvv?

[–] krolden@lemmy.ml 2 points 6 months ago

nfsvers=2 or nfsvers=3 — Specifies which version of the NFS protocol to use. This is useful for hosts that run multiple NFS servers. If no version is specified, NFS uses the highest supported version by the kernel and mount command. This option is not supported with NFSv4 and should not be used.

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/4/html/reference_guide/s2-nfs-client-config-options