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
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
