# NFS Server Test

NFS Server Test is a lightweight Network File System (NFS) testing environment for homelab users to run client and server file-sharing experiments on a local network, not as persistent storage. It is open source and self-hosted, installable on Docker Hub.

Canonical page: https://ourlocalhost.com/app/5467/nfs-server-test

## Description

NFS Server Test is a lightweight Network File System (NFS) testing environment for homelab users to run client and server file-sharing experiments on a local network, not as persistent storage.

## Platform availability

Available on 0 of 10 platforms.

## Health score

16/100 (Low), based on 4 of 4 factors.
- Maintained: 0 (last commit 4141 days ago)
- Popular: 14 (4 GitHub stars)
- Easy to install: 25 (0 install platforms, install notes, Docker image)
- Light to run: 50 (2 GB minimum RAM)

## Links

- Docker Hub: https://hub.docker.com/r/atlassian/nfs-server-test
- GitHub: https://github.com/imp/nfstest

## Common questions

### How can I check whether an NFS test server will hold up under load?

Run high-load read/write and connection testing to reveal problems that may only show up under heavy load.

### Why can an NFS mount become unbearably slow after running for a while?

A high number of test_stateid operations can cause the slowdown, along with hung processes and disk I/O lockups. The source points toward a kernel process-related fix.

### What quick action can restore NFS file sharing if the server stops working properly?

Restarting the NFS service on the server can make it work instantly again.

### Why might systemctl fail to start the NFS server service with a masked unit error?

The nfs-common unit can be masked, which blocks systemctl from starting the service.

---
Source: Our Local Host (https://ourlocalhost.com/app/5467/nfs-server-test), the self-hosted and open-source app directory.
