Menu
▾
▴
#124 Quota RPC does not respect NFS ID mapping
If ID mapping is performed on the NFS client (with kerberized NFS), the UIDs on a client and on a server can differ. Then user identities transported over RPC will query or set wrong UID.
It would be great if there were support of NFS UID mapping to resolve this clash.
Discussion
Anonymous
So ID mapping applies only to NFSv4, doesn't it? The support of the quota RPC protocol for NFSv4 is ... lacking and when I spoke with NFS people about this they told me the right solution is that quota support inside NFSv4 protocol should be used however that doesn't allow to propagate as much information as quota RPC protocol and there are other problems with that (e.g. AFAIK userspace has no way to see quota attributes returned as a result of stat over NFSv4).
WRT ID mapping in particular I was researching that a bit but I see no way how to implement that. The problem is that IDs need to traverse the network as strings - you map local UID to a string (user@realm) on client and then server maps this back to its own UID. However there is no way how to propagate this string over quota RPC protocol.