New answers tagged

0

in your exports file you can put many addresses for a single share /SHARE 192.168.0.12/30(rw,no_root_squash,no_subtree_check) 192.168.0.26/30(rw,no_root_squash,no_subtree_check) this is just an example, you can put every single IP if you want instead of netblocks, or use hostnames.


0

The sole fsid=0 didn't work for me. nfs-utils>=2.4.1 got Add the "[exports] rootdir" option to nfs.conf feature (May 28, 2019): The following patchset adds support for the "rootdir" configuration option for nfsd in the "[exports]" section in /etc/nfs.conf. If a user sets this option to a valid directory path, then nfsd will ...


0

I am thinking the problem could be related to fsgroup permission. (1) Check the readOnly settings in Volume mount (2) Check the securityContexts (fsgroup), Does the PHP user belong to the same UID(33) and Group ID(33)


0

This is just a generic error message (also totally misleading), which points towards a problem in your client kerberos configuration, usually that the GSSAPI service isn't running. Try starting it, or if you have a nss-client.target, enable/start it.


1

I have problems with Error of nfs server daemon fails on booting process. I don't know exactly why, but the problem was from LVM. Before the reboot I remove my LV, VG and PV. I make the mount permanent by adding them to /etc/fstab. After removing my PVs reference from /etc/fstab my problem solved.


1

It turns out that at least up to NFSv4.1, NFS does not have full support for SELinux contexts; you can only set the context per-mount, not per-file/directory. So first we need to allow vncserver access to NFS home directories. This has been fixed upstream in tigervnc v1.12. If that isn't available for the OS, we can just pull the new SELinux configuration ...


0

Okay the solution is quite simple. The fstab line should be like this: server.example.org:/homes /media/nfsv4homes nfs4 rw,defaults 0 0 Mounting works too: mount server.example.org:/homes /mnt/nfshomes


Top 50 recent answers are included