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…

  • Cloud
  • Development
  • Tools & Utilities
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

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

16/100 Low

Maintained
0last commit 4141 days ago
Popular
144 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
502 GB minimum RAM
GitHub stars
4
Open issues
1
Last commit
2015-07-21
License
GPL-2.0
Activity
stale

Checked 15 days ago - source: GitHub (imp/nfstest)

Resources & Compatibility

Minimum requirements: 2 GB RAM, 10 GB disk. ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set certificate and tax details first Export NFSE_CERT_PATH, NFSE_CERT_SENHA, NFSE_CNPJ, and NFSE_COD_MUN before running the example, because the app needs your A1 certificate (a digital identity file) and municipality code to act on your behalf. It also runs in dry-run mode by default, so set NFSE_CONFIRMA_EMISSAO=yes or it will not actually send anything. source
  • Install the example's dependencies Run npm install in the example folder, and build the parent repository if the local package is not found. This gives the example the TypeScript tools and the open-nfse package it expects, preventing an immediate startup failure. source
  • Keep the certificate file secure Store your .pfx certificate file (a password-protected digital certificate) and its password safely, because the client reads that file to sign fiscal documents. If the file is missing or the password is wrong, the app cannot authenticate and will stop. source
  • Use the nfstest utilities After deploying, use the included nfstest utilities to run PASS/FAIL NFS tests, mount or unmount shares, create test files, and capture packet traces. source

Fetched 41 days ago - each note links to its source

Alternatives

No alternatives collected yet.

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.

Answers sourced from hardforum.com, serverfault.com, www.reddit.com, www.reddit.com

Community

Collected 48 days ago - public community threads