[Gluster-users] boot auto mount NFS-Ganesha exports failed

Renaud Fortier Renaud.Fortier at fsaa.ulaval.ca
Fri Mar 13 13:38:43 UTC 2020

Hi community,
Maybe someone could help me with this one: half the time, mounting nfs-ganesha NFS4 exports failed at boot. I've seach a lot about this problem but because it doesn't happen at every boot it's difficult to pinpoint the exact problem. It mount perfectly after boot is completed.

-Debian 9 (uptodate) on all Gluster servers and clients (4 apache2 web servers).
-Gluster version 6.7
-NFS-Ganesha version 2.8.3
-NFS 4.2
-fstab exemple: /data nfs4 noatime,nodiratime,vers=4.2,_netdev 0 0
-NFS-Ganesha export exemple:
    Export_Id = 2;
    Path = "/dev";
    Pseudo = "/dev";
    Access_Type = RW;
    Squash = No_root_squash;
    Disable_ACL = true;
    Protocols = "4";
    Transports = "UDP","TCP";
    SecType = "sys";
    FSAL {
        Name = "GLUSTER";
       Hostname = localhost;
        Volume = "dev";

-Dmesg log: NFS: nfs4_discover_server_trunking unhandled error -512. Exiting with error EIO
-Systemd log:
    systemd[1]: Failed to mount /data.
    systemd[1]: Dependency failed for Remote File Systems.
    systemd[1]: remote-fs.target: Job remote-fs.target/start failed with result 'dependency'.
    systemd[1]: data.mount: Unit entered failed state.

I tried to reproduce the same problem with a test machine but it mount perfectly at every reboot. Then, I'm pretty sure the problem is on my clients. Also, no problem with fuse mount.
Any help or direction to follow will be greatly appreciated.
Thank you

Renaud Fortier
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20200313/39064c78/attachment.html>

More information about the Gluster-users mailing list