NFSv4 behaviour on unknown users
Subsystems (2)
Hello all
we recently moved to nfsv4 from v3.
I'm currently using idmapd and not kerberos.
I noticed that now, with idmapd (and with idmapd is the only way I know for configuring nfsv4 for now), users that are not known at server side are squashed to nobody / nogroup (65534 / 65534). And a chown by root from the client fails if the user is not known at server side.
That's a problem... now we need ldap everywhere...
We were often using NFS for exporting some diskspace to machines on an as-needed basis, so this new behaviour complicates the things greatly for us :-/
It's almost easier to setup iSCSI targets now :-((
Is there a way to have nfsv4 with the behaviour of users of nfsv3, that is, using numeric IDs instead of the names, like: "nfsserver, don't care if you don't know the user, just give me the numeric ID for the file..."
Thank you
Quoted 5 lines · Spelic
Hello all
we recently moved to nfsv4 from v3.I'm currently using idmapd and not kerberos.
Quoted 7 lines
I noticed that now, with idmapd (and with idmapd is the only way I know for configuring nfsv4 for now), users that are not known at server side are squashed to nobody / nogroup (65534 / 65534).
And a chown by root from the client fails if the user is not known at server side.That's a problem... now we need ldap everywhere...
Hello!
We also have a few environments using libnss-mysql currently on NFSv3, and in this case, idmapping is pointless and just adds useless work, since all of the clients already have exactly the same user mappings, by design. In fact, the NFS servers don't even know about the users for the files they serve, and this is fine. We'd have to set up libnss-mysql on them for NFSv4 to work, all just so NFSv4 can have names on the wire.
This came up before; e.g. http://linux.derkeiler.com/Mailing-Lists/Kernel/2009-09/msg01071.html
(I hijacked the thread about the credcache hash bucket size, which is
also an issue we ran into as well, but which also affects NFSv3.)
I tried to write the NFSv4 spec people, but didn't get any reply. I can see maybe why they would want to do this by default, but it's not like people don't already have years of experience with how NFSv3 and earlier worked, and I still think should at least be a way to request that behaviour.
Simon-
Quoted 7 lines · Simon Kirby
...
I tried to write the NFSv4 spec people, but didn't get any reply. I can see maybe why they would want to do this by default, but it's not like people don't already have years of experience with how NFSv3 and earlier worked, and I still think should at least be a way to request that behaviour.
Yeah!!!
currently it sucks... er...
I don't understand... never before I came across a "new version" of a software or a protocol which allows to do many fewer things than the older version. This sucks. Lots of use cases for NFS here are totally lost.
I'm thinking that even if I'd setup LDAP for everything here, things would not be easy, because we have server1 which has certain users and groups, server2+server3 which are for a different project and have different users and groups etc... and now we need to have the NFS server understand all those sets of users simultaneously, but the various servers only need to understand theirs and the other people should not be able to log in! Maybe it's possible (I don't know how), but looks like a major headache. And now we probably cannot even have more than one LDAP server any longer: all LDAP probably needs to be centralized on a single machine which is where the NFS server(s) authenticate... it looks like a real problem for the independence of projects... and I really fear to think of what will happen if that machine fails!
I'd be glad to go back to NFS version 3 but we need nfs on infiniband rdma now, and afaik it's only available in version 4.
If it's still possible to change the specs or break them, well... you sure have my vote!
Thank you
S.
Quoted 1 line · Spelic
I'd be glad to go back to NFS version 3 but we need nfs on infiniband rdma now, and afaik it's only available in version 4.
NFS/RDMA is also available for NFSv3, in fact that's where it was first fully implemented. Whether it is well-supported upstream is another question entirely.
Signature · 2 lines
Chuck Lever chuck[dot]lever[at]oracle[dot]com