I have googled for setup advice on NFSv4 specifically for F11 - but I have not yet found a good reference including pitfall lists and itemised steps... does anyone know of a good (step by step) reference for setting up both NFSv4 server and client in F11?
On Thu, Oct 15, 2009 at 1:00 PM, Mike Cloaked mike.cloaked@gmail.com wrote:
I have googled for setup advice on NFSv4 specifically for F11 - but I have not yet found a good reference......
______
Hmm... please try again. :-)
http://lmgtfy.com/?q=Fedora+NFS+howto
Something to keep in mind: Fedora uses rpcbind in place of portmap.
~af
On 10/15/2009 05:21 PM, Aldo Foot wrote:
On Thu, Oct 15, 2009 at 1:00 PM, Mike Cloaked mike.cloaked@gmail.com wrote:
I have googled for setup advice on NFSv4 specifically for F11 - but I have not yet found a good reference......
Hmm... please try again. :-)
AF: ----- Got the smiley but
o) Your google is not even what the OP asked for ... at all.
Cloaked: ------- o) I didnt find anything specific to F11 - however, nfs4 has been around a while - so it shud not need to be fedora (or f11) specific at all.
o) here is a brief page or 2 (sorry for wrapped links)
http://fedoraunity.org/solved/post-install-solutions/nfsv4-fedora
http://www.novell.com/communities/node/3787/configuring-nfsv4-server-and-cli...
https://help.ubuntu.com/community/NFSv4Howto
gene/
Mail Lists-3 wrote:
AF:
Got the smiley but
o) Your google is not even what the OP asked for ... at all.
Cloaked:
o) I didnt find anything specific to F11 - however, nfs4 has been around a while - so it shud not need to be fedora (or f11) specific at all.
o) here is a brief page or 2 (sorry for wrapped links)
http://fedoraunity.org/solved/post-install-solutions/nfsv4-fedora
http://www.novell.com/communities/node/3787/configuring-nfsv4-server-and-cli...
https://help.ubuntu.com/community/NFSv4Howto
gene/
OK thanks - however one of the reasons that I asked the original question was that a) there are indeed a number of references around, but some refer to using portmap (like in your first ref), but I understand that this is deprecated in favour of rpcbind - and I believe that this is running by default in recent versions of Fedora. b) it is not clear whether there are any selinux gotchas so I was hoping that someone would respond saying that they had set up nfs server and client and that either it worked great, or that there were issues - and then say what the workarounds are, or refer to a link explaining how to deal with it. c) I was hoping to see a single article that included automounting nfs shares rather than permanently mounting them via fstab since for my use case I did not need to tie up resources except for short times when the nfs share was needed. d) I was also hoping to see cases where nfs3 had been used and the sysadmin moved over to nfs4 - and then find what the problems, if any, where using version 4 rather than 3. Hopefully easier since a single port must be opened up in the firewall rather than multiple ports for nfs v3
I was also hoping to gauge whether there were many people who read this list who are nfs4 rather than 3 users - or whether the predominant use is still nfs3
Mike Cloaked wrote:
a) there are indeed a number of references around, but some refer to using portmap (like in your first ref), but I understand that this is deprecated in favour of rpcbind - and I believe that this is running by default in recent versions of Fedora. b) it is not clear whether there are any selinux gotchas so I was hoping that someone would respond saying that they had set up nfs server and client and that either it worked great, or that there were issues - and then say what the workarounds are, or refer to a link explaining how to deal with it. c) I was hoping to see a single article that included automounting nfs shares rather than permanently mounting them via fstab since for my use case I did not need to tie up resources except for short times when the nfs share was needed. d) I was also hoping to see cases where nfs3 had been used and the sysadmin moved over to nfs4 - and then find what the problems, if any, where using version 4 rather than 3. Hopefully easier since a single port must be opened up in the firewall rather than multiple ports for nfs v3
I was also hoping to gauge whether there were many people who read this list who are nfs4 rather than 3 users - or whether the predominant use is still nfs3
Excuse the odd typo in the previous post - actually the linuxhomenetworking link that google finds at http://www.linuxhomenetworking.com/wiki/index.php/Quick_HOWTO_:_Ch29_:_Remot...
is quite a good guide but does not mention selinux... perhaps selinux works so transparently now that it does not need mentioning!
On Fri, 2009-10-16 at 00:31 -0700, Mike Cloaked wrote:
d) I was also hoping to see cases where nfs3 had been used and the sysadmin moved over to nfs4 - and then find what the problems, if any, where using version 4 rather than 3. Hopefully easier since a single port must be opened up in the firewall rather than multiple ports for nfs v3
I was also hoping to gauge whether there were many people who read this list who are nfs4 rather than 3 users - or whether the predominant use is still nfs3
FWIW, I've switched our school system over to nfs4 from nfs3 when I deployed the Fedora 11 image. There were two reasons:
* nfs3 file locking seriously sucks. When someone opened OpenOffice, had a crash, and then attempted to open OpenOffice again, it would segfault, no matter which computer was used. The only solution was to rm ~/.openoffice.org. Some problem with firefox. * There was nothing stopping random computers on the network from connecting to the server. With nfs4 being restricted to one port, I've been able to turn on ipsec authentication for that port only.
There have been two problems with nfs4:
* Usernames now have to be matched using rpcidmapd where before all I needed to do was make sure the UID's matched up (using LDAP). * There is now some funky POSIX->NFS->POSIX acl conversion going on, rather than the (admittedly hacked on) POSIX acls that were built-in to nfs3. It just means I can't see the acls on the client using standard getfacl and setfacl tools.
Hope that helps.
Jonathan
Jonathan Dieter-2 wrote:
FWIW, I've switched our school system over to nfs4 from nfs3 when I deployed the Fedora 11 image. There were two reasons:
- nfs3 file locking seriously sucks. When someone opened OpenOffice,
had a crash, and then attempted to open OpenOffice again, it would segfault, no matter which computer was used. The only solution was to rm ~/.openoffice.org. Some problem with firefox.
- There was nothing stopping random computers on the network from
connecting to the server. With nfs4 being restricted to one port, I've been able to turn on ipsec authentication for that port only.
There have been two problems with nfs4:
- Usernames now have to be matched using rpcidmapd where before all I
needed to do was make sure the UID's matched up (using LDAP).
- There is now some funky POSIX->NFS->POSIX acl conversion going on,
rather than the (admittedly hacked on) POSIX acls that were built-in to nfs3. It just means I can't see the acls on the client using standard getfacl and setfacl tools.
Hope that helps.
Jonathan
Thank you Jonathan - that is exactly the kind of feedback I was hoping to get - and useful. Of course setting up the basics of the exports etc is one thing, but tying in authentication as well as using acls is not that obvious (to me at any rate!) so a clear guide showing how to do it is still needed.