Search Results

Your exports syntax is incorrect – you cannot have any spaces in the option list. Try: /home/MYUSER/Documents 192.168.0.2(rw,sync,no_subtree_check)

You need to give yourself write permissions on the /srv/www/htdocs/restoredb directory in order to create or delete files.

(Doing so makes the server's ufw configuration irrelevant, and in fact you should close the NFS port unless you're using Kerberos security.) …

Microsoft doesn't really seem to care about the NFS client in Windows – it seems to be pretty much stuck in the "Windows 2000 and Interix" era. …

Well, you're explicitly disabling those checks – that's what no_subtree_check does. Switch it back to subtree_check. (Pay attention to the performance notes in the exports(5) manual page, though.)

Since the NFS home directories are lazy-mounted, will this actually result in services being started on boot? … (This will not quite work if you're using NFS with Kerberos.) If the lazy-mount is triggered using PAM, it will happen if /etc/pam.d/systemd-user invokes the necessary PAM modules. …

RPC, used by NFS, usually supports two authentication mechanisms: AUTH_UNIX (sec=sys, by user ID) and AUTH_GSS (sec=krb5/krb5i, by Kerberos ticket). … As for Samba: I am reading a lot about that it doesn't perform so well compared to NFS. It somewhat depends on the client and server implementations. …

Is it possible that I lose user data reconfiguring partition table using mkfs.xfs? Yes, in fact that is literally what mkfs tools do: they always create a brand new filesystem with no data in it. …

Your tunnel goes backwards: if the Linux server wants to mount the filesystem, then ssh on the Synology doesn't need to listen on any ports at all (why would it, if the real NFS service is already doing … Instead the tunnel's "listen" side needs to be on the Linux server (i.e. you want an SSH -R tunnel), which will then connect to the real NFS listener on the Synology. ssh -R 22049:localhost:2049 [email protected] …

As far as I can tell, that's not a TCP nor UDP port number; it's the RPC transaction ID. (See print-nfs.c:nfsreply_print in tcpdump sources.) tcpdump sometimes tends to use very terse output; conside …

/srv/nfs/usr-local mount --bind /var/fea/jobs /srv/nfs/fea-jobs (for fstab, /usr/local /srv/nfs/usr-local none bind 0 0) In your current configuration, /usr/local is being used as the NFS root (with nat149app … See section 7 - NFS Server Name Space of RFC 3530 - NFS version 4. …

You could merge the home directories and mount them from a file server via NFS (possibly using autofs), or you could keep them local and use NFS for non-$HOME data only. …

This will 1) prevent nfs-server-generator from adding systemd dependencies for that path, and 2) cause exportfs to verify that the filesystem is mounted before marking it for export. … (The auto-generated dependencies can be seen with systemctl cat nfs-server, with the extra file "order-with-mounts.conf" shown at the end, and refreshed with systemctl daemon-reload.) …

Why my NFS server is stuck in active(exited) Because the NFS server lives in the kernel and does not have a userspace process. … To check whether the kernel NFS server is actually running, run ps axf or htop and search for kthreads named "[nfsd]". …

Your NFS mount uses vers=3 meaning NFSv3, which does not support any ACL configuration as far as I know. … The Linux NFSv4 servers will translate between POSIX ACLs on disk and NFSv4 ACLs on the network, although the Linux NFS client unfortunately doesn't do the opposite translation. …