Good morning Arnau, I reached out to one of our NFS Experts and this was his response: ---begin--paste-- Simple we always look for the exact path first... note you have /ifs    <--- all-dirs enabled  which catches all other NON defined nfs exports in /ifs/xxxxx  So in NFS we use the mountd daemon, that basically manages the exports file..  The client will make a request like  mount  CALL MNT /ifs/Users mount REPLY /ifs/Users FH.... ---end--paste--  The other thing is that I'd always be very wary of is having an /ifs NFS export. Unless you absolutely have to have it for something, it is generally frowned upon.  It is present in new cluster installations just for the purpose of loading code or firmware updates during initial configuration.  You'll never want clients to use it, and anything that you might want to do as an administrator through that export you can likely do directly on the cluster itself.  Hope this helps; Chris Klosterman Senior SA, EMC Isilon Offer & Enablement Team chris.klosterman[NAME].com twitter: [NAME]
Hello all,  In a scenario where you define two exports like:  /ifs 192.168.0.4 (rw) /ifs/users 192.168.0.0/24 (ro)  and you mount /ifs/users from 192.168.0.4, which one should take precedence and why?  In our case the second one (ro) is the one that the client uses for mounting but we would like it to use the first (and more generic) one (with rw).  How does the precedence works? Many thanks in advance, Arnau
export file precedence