Chris's Wiki :: blog/unix/NFSReaddirAndDType Commentshttps://utcc.utoronto.ca/~cks/space/blog/unix/NFSReaddirAndDType?atomcommentsDWiki2018-09-03T03:25:08ZRecent comments in Chris's Wiki :: blog/unix/NFSReaddirAndDType.By Stephen on /blog/unix/NFSReaddirAndDTypetag:CSpace:blog/unix/NFSReaddirAndDType:d08fda61da8592b4fb9bf10623713be8f2a30e2dStephen<div class="wikitext"><p>We found nfs v4 both easy to use and a complete mess.</p>
<p>I help manage some 500+ nfs clients and a handful of servers. We don't use krb so every nfs export is sec=sys. At some point centos and ubuntu switched from v3 by default to v4.1 by default. We mostly didn't notice. Where we did have problems the "fix" was to force the client to use v3. We often could not determine the magic needed to make the v4 mount work. Our guess was something in idmap was wrong on one side or the other. In most cases the client only able to read/write files as user nobody. </p>
<p>In the cases where nfs v4 just works the client is usually a generic Centos 7 or Ubuntu 16.04 or 18.04 with ldap users (ldap auth and id/gid lookup). We also have a few other clients with older versions of Linux, *BSD, or something proprietary. While some of these work, it is usually these ones that fail.</p>
</div>2018-09-03T03:25:08Z