Discussion:
[Gluster-users] NFS-Ganesha question
Renaud Fortier
2018-10-15 14:14:04 UTC
Permalink
Hi,
We are currently facing a strange behaviour with our cluster. Right now I'm running bitrot scrub against the volume but I'm not sure it will help finding the problem. Anyway, my question is about nfs-ganesha and NFSv4. Since this strange behaviour begun, I read alot and I found that idmapd is needed for NFSv4. If I run rpcinfo or ps -ef |grep idmapd on our nodes, I don't see it.

Is rpc.idmapd supposed to be running when using nfs-ganesha 2.6.3 with gluster 4.1.5 ?

Thank you
Jiffin Tony Thottan
2018-10-16 05:09:00 UTC
Permalink
CCing ganesha list as well
Post by Renaud Fortier
Hi,
We are currently facing a strange behaviour with our cluster. Right
now I’m running bitrot scrub against the volume but I’m not sure it
will help finding the problem. Anyway, my question is about
nfs-ganesha and NFSv4. Since this strange behaviour begun, I read alot
and I found that idmapd is needed for NFSv4. If I run rpcinfo or ps
–ef |grep idmapd on our nodes, I don’t see it.
Is rpc.idmapd supposed to be running when using nfs-ganesha 2.6.3 with gluster 4.1.5 ?
IMO rpc.idmap as a service is not required for ganesha, but ganesha uses
apis from "libnfsidmap"  for id mapping for confirming the same

CCing ganesha devel list as well.

--
Jiffin
Post by Renaud Fortier
Thank you
_______________________________________________
Gluster-users mailing list
https://lists.gluster.org/mailman/listinfo/gluster-users
Daniel Gryniewicz
2018-10-16 12:00:02 UTC
Permalink
Post by Jiffin Tony Thottan
CCing ganesha list as well
Post by Renaud Fortier
Hi,
We are currently facing a strange behaviour with our cluster. Right
now I’m running bitrot scrub against the volume but I’m not sure it
will help finding the problem. Anyway, my question is about
nfs-ganesha and NFSv4. Since this strange behaviour begun, I read alot
and I found that idmapd is needed for NFSv4. If I run rpcinfo or ps
–ef |grep idmapd on our nodes, I don’t see it.
Is rpc.idmapd supposed to be running when using nfs-ganesha 2.6.3 with gluster 4.1.5 ?
IMO rpc.idmap as a service is not required for ganesha, but ganesha uses
apis from "libnfsidmap"  for id mapping for confirming the same
idmapd is used to convert client usernames/IDs into server
usernames/IDs. This allows things like a user with UID 100 on one
client to map to the same user with UID 200 on another client. It's
not, strictly speaking, necessary; but it's very nice to have,
especially in large environments with diverse clients.

NFSv4 will work without it.

Daniel
Malahal Naineni
2018-10-16 14:11:41 UTC
Permalink
Yes, ganesha Daemon doesn't use idmapd Daemon. In fact, some distros start
knfsd when you start idmapd Daemon so it is better not to start idmapd at
all.
Post by Jiffin Tony Thottan
CCing ganesha list as well
Hi,
We are currently facing a strange behaviour with our cluster. Right now
I’m running bitrot scrub against the volume but I’m not sure it will help
finding the problem. Anyway, my question is about nfs-ganesha and NFSv4.
Since this strange behaviour begun, I read alot and I found that idmapd is
needed for NFSv4. If I run rpcinfo or ps –ef |grep idmapd on our nodes, I
don’t see it.
Is rpc.idmapd supposed to be running when using nfs-ganesha 2.6.3 with gluster 4.1.5 ?
IMO rpc.idmap as a service is not required for ganesha, but ganesha uses
apis from "libnfsidmap" for id mapping for confirming the same
CCing ganesha devel list as well.
--
Jiffin
Thank you
_______________________________________________
_______________________________________________
Loading...