Description of problem: Observing ""Failed to open v4 recovery dir (/var/lib/nfs/ganesha//v4recov), errno=13" " message in ganesha.log when ganesha cluster goes to 90 seconds of GRACE period and selinux is in ENFORCING mode Version-Release number of selected component (if applicable): selinux-policy-3.13.1-192.el7_5.3.noarch # rpm -qa | grep ganesha nfs-ganesha-gluster-2.5.5-4.el7rhgs.x86_64 glusterfs-ganesha-3.12.2-7.el7rhgs.x86_64 nfs-ganesha-2.5.5-4.el7rhgs.x86_64 How reproducible: 100% Steps to Reproduce: 1.Create 4 node ganesha cluster.Sel Selinux to ENFORCING node in all the 4 nodes 2.Reboot any one node. Actual results: Post reboot,when ganesha cluster goes to 90 seconds to GRACE period,observing "Failed to open v4 recovery dir (/var/lib/nfs/ganesha//v4recov), errno=13" messages in ganesha.log ============= 12/04/2018 17:34:55 : epoch 9e940000 : dhcp46-184.lab.eng.blr.redhat.com : ganesha.nfsd-23203[dbus_heartbeat] nfs4_start_grace :STATE :EVENT :NFS Server Now IN GRACE, duration 90 12/04/2018 17:34:55 : epoch 9e940000 : dhcp46-184.lab.eng.blr.redhat.com : ganesha.nfsd-23203[dbus_heartbeat] nfs4_start_grace :STATE :EVENT :NFS Server recovery event 5 nodeid -1 ip 12/04/2018 17:34:55 : epoch 9e940000 : dhcp46-184.lab.eng.blr.redhat.com : ganesha.nfsd-23203[dbus_heartbeat] fs_read_recov_clids_takeover :CLIENT ID :EVENT :Recovery for nodeid -1 dir (/var/lib/nfs/ganesha//v4recov) 12/04/2018 17:34:55 : epoch 9e940000 : dhcp46-184.lab.eng.blr.redhat.com : ganesha.nfsd-23203[dbus_heartbeat] fs_read_recov_clids_impl :CLIENT ID :EVENT :Failed to open v4 recovery dir (/var/lib/nfs/ganesha//v4recov), errno=13 12/04/2018 17:34:55 : epoch 9e940000 : dhcp46-184.lab.eng.blr.redhat.com : ganesha.nfsd-23203[dbus_heartbeat] fs_read_recov_clids_takeover :CLIENT ID :EVENT :Failed to read v4 recovery dir (/var/lib/nfs/ganesha//v4recov) 12/04/2018 17:36:28 : epoch 9e940000 : dhcp46-184.lab.eng.blr.redhat.com : ganesha.nfsd-23203[reaper] nfs_in_grace :STATE :EVENT :NFS Server Now NOT IN GRACE ========================== Expected results: There should not be any failures when ganesha nodes goes to 90 seconds of GRACE period Additional info: These messages are not been observed when selinux is set to PERMISSIVE mode.
What is the ownership of the recovery directory? This sounds like an issue with ownership of the directory and maybe some SELinux stuff.
Can you include ls -Z output?
Okay, so I'm pretty sure that when SELinux is enforcing, the files need to be ganesha_t not fusefs_t.