NFS Export

maggo123 · 01-19-2019, 06:19 AM

Hi,

I exported /srv/nfs

/etc/exports
/srv/nfs/ *(rw,no_root_squash,fsid=0)

I can mount /srv/nfs and i can see the Subfolder P01. However, under P01 there are additional subfolders which i can´t see from the client. What i am doing wrong?

Thanks!

PS: Sorry - i am a noob

wpeckham · 01-19-2019, 06:49 AM

Everyone is a noob at some time. Do not worry about that.

What ownership and permissions are on these folders and subfolders? Perhaps the permissions are at issue.

maggo123 · 01-19-2019, 08:12 AM

Hi,

thank you!

Those are the permissions of P01

drwxr-xr-x 9 root root 122 Jan 19 10:10 P01

Those are the permissions of the subfolder

drwxr-xr-x 2 root root 6 Jan 17 18:57 Music

dc.901 · 01-19-2019, 08:50 AM

Quote:

Originally Posted by maggo123

Hi,

I exported /srv/nfs

/etc/exports
/srv/nfs/ *(rw,no_root_squash,fsid=0)

I can mount /srv/nfs and i can see the Subfolder P01. However, under P01 there are additional subfolders which i can´t see from the client. What i am doing wrong?

Is that the only line in your exports? Reason I ask is because if you have more than one export with same fsid, it will cause problems.

MadeInGermany · 01-19-2019, 09:26 AM

Are they simple subdirectories i.e. in the same filesystem?

Code:

df /srv/nfs /srv/nfs/*

Rickkkk · 01-19-2019, 11:13 AM

Hello maggo123 - welcome to LQ.

I find that the following options work well for me when exporting entire directory trees:

Code:

FROM MY /etc/exports FILE:

.....

/dir/subdir xxx.xxx.xxx.0/24(rw,nohide,insecure,no_subtree_check,async)

....

The first string in the options I use is simply the IP address range to which I permit access from nfs clients. The meaning of the other options can be easily looked up, so I'll leave that part to you.

The Arch Linux wiki entry on nfs is an excellent source of information.

Make sure that you check the permissions on the server, as recommended by wpeckham in post #2.

Let us know how it goes.

maggo123 · 01-19-2019, 11:15 AM

Quote:

Originally Posted by dc.901

Is that the only line in your exports? Reason I ask is because if you have more than one export with same fsid, it will cause problems.

Jepp, that´s the only entry. For what is The FSID used?

maggo123 · 01-19-2019, 11:16 AM

Quote:

Originally Posted by Rickkkk

Hello maggo123 - welcome to LQ.

I find that the following options work well for me when exporting entire directory trees:

Code:

FROM MY /etc/exports FILE:

.....

/dir/subdir xxx.xxx.xxx.0/24(rw,nohide,insecure,no_subtree_check,async)

....

The first string in the options I use is simply the IP address range to which I permit access from nfs clients. The meaning of the other options can be easily looked up, so I'll leave that part to you.

The Arch Linux wiki entry on nfs is an excellent source of information.

Make sure that you check the permissions on the server, as recommended by wpeckham in post #2.

Let us know how it goes.

Thanks - will give it a try

ehartman · 01-19-2019, 01:12 PM

Quote:

Originally Posted by maggo123

*(rw,no_root_squash

No answer to your problem, but I admit the combination of rw and no_root_squash gives me the shivers. This means that every system that
a) can see the share (and thus mount it - you do not restrict it)
b) with a user that can become root or has sudo rights
can modify or delete files ON the share, as they now got superuser rights ON your share.

In my network no_root_squash is only used on read-only exports (so that shares honor the suid and/or sgid bits on executables).

Code:

/opt  192.168.178.0/24(ro,async,no_subtree_check,no_root_squash)

I once had a case where a remote University didn't restrict ITS NFS exports, so that I could mount them even at our location in Delft. Luckily I did mount it read-only so even in error I couldn't mess up their system (the export was meant for their students only).