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

2020-03-15 Thread Soumya Koduri

Hi,

Since its working on your test machine, most likely could be NFS 
client-side issue. Please check if there are any kernel fixes between 
those versions which may have caused this.


I see similar issue reported in below threads [1] [2]. As suggested 
there, could you try disabling kerberos module and specify "sec=sys" 
during mount. If the issue persists, please use "-vvv" option during 
mount to get more verbose output.



Thanks,
Soumya

[1] 
https://askubuntu.com/questions/854591/nfs-not-mounting-since-upgrading-from-14-04-to-16-04
[2] 
https://superuser.com/questions/1201159/nfs-v4-nfs4-discover-server-trunking-unhandled-error-512-after-reboot/1207346


On 3/13/20 7:08 PM, Renaud Fortier wrote:

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: 192.168.11.90:/dev /data nfs4 
noatime,nodiratime,vers=4.2,_netdev 0 0


-NFS-Ganesha export exemple:

EXPORT {

     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






Community Meeting Calendar:

Schedule -
Every Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968

Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users







Community Meeting Calendar:

Schedule -
Every Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968

Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users


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

2020-03-13 Thread Renaud Fortier
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: 192.168.11.90:/dev /data nfs4 
noatime,nodiratime,vers=4.2,_netdev 0 0
-NFS-Ganesha export exemple:
EXPORT {
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




Community Meeting Calendar:

Schedule -
Every Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968

Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users