Network File System: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary Tag: Manual revert |
mNo edit summary |
||
| Line 15: | Line 15: | ||
/mnt/data 192.168.0.0/24(rw,sync) | /mnt/data 192.168.0.0/24(rw,sync) | ||
* If you want the share to be accessible from non root users (it's needed for access on Android for instance, or on Batocera), you need to add the insecure flag: | |||
/mnt/data 192.168.0.8(ro,sync,no_subtree_check) | |||
* This would grant access to all IPs in range 192.168.0.*. You may need to restart the server (/etc/init.d/nfs restart) for the share to be actually added. | * This would grant access to all IPs in range 192.168.0.*. You may need to restart the server (/etc/init.d/nfs restart) for the share to be actually added. | ||
Latest revision as of 09:23, 17 March 2025
Crashed NFS server
- You can unmount a non-responsive NFS server by using the -l (lazy) option:
umount -l /mnt/data
Stale file handle error
- If you get this error, and are unable to mount the share on the client, just restart the server. For instance on Debian:
sudo systemctl restart nfs-server
- Just edit /etc/exports:
/mnt/data 192.168.0.0/24(rw,sync)
- If you want the share to be accessible from non root users (it's needed for access on Android for instance, or on Batocera), you need to add the insecure flag:
/mnt/data 192.168.0.8(ro,sync,no_subtree_check)
- This would grant access to all IPs in range 192.168.0.*. You may need to restart the server (/etc/init.d/nfs restart) for the share to be actually added.