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.
On Tue, 16 Oct 2018, 5:26 pm Jiffin Tony Thottan, <jthottan(a)redhat.com>
wrote:
CCing ganesha list as well
On Monday 15 October 2018 07:44 PM, Renaud Fortier wrote:
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
_______________________________________________
Gluster-users mailing
listGluster-users@gluster.orghttps://lists.gluster.org/mailman/listinfo/gluster-users
_______________________________________________
Devel mailing list -- devel(a)lists.nfs-ganesha.org
To unsubscribe send an email to devel-leave(a)lists.nfs-ganesha.org