Network File System: Difference between revisions
Jump to navigation
Jump to search
(Created page with "= Crashed NFS server = * You can unmount a non-responsive NFS server by using the -l (lazy) option: umount -l /mnt/data") |
mNo edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 3: | Line 3: | ||
* You can unmount a non-responsive NFS server by using the -l (lazy) option: | * You can unmount a non-responsive NFS server by using the -l (lazy) option: | ||
umount -l /mnt/data | 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 | |||
= Adding a NFS share = | |||
* Just edit /etc/exports: | |||
/mnt/data 192.168.0.0/24(rw,sync) | |||
* 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 12:53, 6 May 2024
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)
- 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.