Triode,
A couple of other questions re: the actions triggered on the "stoarge"
page:
1. Removing a CIFS mount does not remove the associated "credentials
file" - should it?
2. First time you add a NFS additional services are enabled and started.
If another new NFS is added the same services are enabled and started
again. Or, if the first NFS mount is removed and then added again same
extra services are enabled and started again. Does this matter?
3. Using a NFS share can result in this timeout message appearing in
journalctl:
Code:
--------------------
[root@alarm credentials]# journalctl | grep "AUTH_GSS upcall timed out"
Jul 13 17:26:40 alarm kernel: RPC: AUTH_GSS upcall timed out.
Jul 13 17:29:00 alarm kernel: RPC: AUTH_GSS upcall timed out.
Jul 13 20:34:04 alarm kernel: RPC: AUTH_GSS upcall timed out.
Jul 13 21:06:23 alarm kernel: RPC: AUTH_GSS upcall timed out.
Jul 13 21:48:56 alarm kernel: RPC: AUTH_GSS upcall timed out.
Jul 13 22:18:38 alarm kernel: RPC: AUTH_GSS upcall timed out.
Jul 13 22:30:32 alarm kernel: RPC: AUTH_GSS upcall timed out.
Jul 14 17:30:36 alarm kernel: RPC: AUTH_GSS upcall timed out.
--------------------
This appears related to arhclinux wiki entry on nfs and the need for
>
> Clients with a kernel version prior to 3.12.7-2 (the current linux-lts
> for example) MUST start rpc-gssd.service to avoid an approx 15 seconds
> delay with an accompanying error in dmesg that reads, "RPC: AUTH_GSS
> upcall timed out" due to a kernel bug.
>
4. When selecting mount type nfs, the share should not be mounted as
nfs4 as it currently is. An NFs mount should default to vers=3.
------------------------------------------------------------------------
Krisbee's Profile: http://forums.slimdevices.com/member.php?userid=59080
View this thread: http://forums.slimdevices.com/showthread.php?t=101624
_______________________________________________
unix mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/unix
