NFSTEST_PNFS(1)

πŸ’– NFSTEST_PNFS πŸ’–

okay bestie, welcome to nfstest_pnfs β€” it's part of the nfstest fam, version 1.5, and it's the girl who checks that your pNFS setup is actually doing the thing. pull up a chair, grab a strawberry πŸ“, and let's get into it.


✨ NAME ✨

nfstest_pnfs β€” basic pNFS functional tests. that's it, that's the vibe. it runs the tests, it tells you if pNFS is slaying or flopping.


🌸 SYNOPSIS 🌸

nfstest_pnfs --server <server> [options]

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so here's the whole point of her: she verifies basic pNFS functionality for a file β€” and yes, that means both READ and WRITE, no picking favorites. πŸ’…

she also checks what happens when you open a second file within the same mount and when you have a lock on the file. because pNFS gotta behave even when things get complicated, you know?

and then β€” this is the part I'm obsessed with β€” she verifies basic pNFS functionality for a file opened for both READ and WRITE at the same time, while reading the file first and then writing to it, or the other way around: writing to the file first and then reading the file. both directions, both orders, no cap. 🫢

all of these tests verify that pNFS and NFSv4.1 are functioning properly. so like, if something's broken, she WILL find it. main character energy fr fr.


πŸ’… OPTIONS πŸ’…

general girly options

  • --version β€” shows the program's version number and dips. bye! πŸ‘‹
  • -h, --help β€” shows this help message and exits. iconic of her tbh.
  • -f FILE, --file=FILE β€” the file where options are specified, besides the system wide file /etc/nfstest, the user wide file $HOME/.nfstest, or the .nfstest file in the current directory. so many places to spill your settings ✨

🌈 NFS specific options 🌈

  • -s SERVER, --server=SERVER β€” server name or IP address. the whole reason we're here bestie.
  • -e EXPORT, --export=EXPORT β€” exported file system to mount [default: '/']
  • --nfsversion=NFSVERSION β€” NFS version, e.g., 3, 4, 4.1, etc. [default: 4.1]
  • -m MTPOINT, --mtpoint=MTPOINT β€” mount point [default: '/mnt/t']
  • -p PORT, --port=PORT β€” NFS server port [default: 2049]
  • --proto=PROTO β€” NFS protocol name [default: 'tcp']
  • --sec=SEC β€” security flavor [default: 'sys']
  • --nconnect=NCONNECT β€” multiple TCP connections option [default: '1']
  • -o MTOPTS, --mtopts=MTOPTS β€” mount options [default: 'hard,rsize=4096,wsize=4096']
  • --datadir=DATADIR β€” data directory where files are created; the directory is created on the mount point [default: '']

πŸ“ Logging options πŸ“

  • -v VERBOSE, --verbose=VERBOSE β€” verbose level for debug messages [default: 'opts|info|dbg1|dbg2|dbg3']
  • --tverbose=TVERBOSE β€” verbose level for test messages [default: '1']
  • --createlog β€” create log file
  • --rexeclog β€” create rexec log files
  • --warnings β€” display warnings
  • --tag=TAG β€” informational tag, it is displayed as an INFO message [default: '']
  • --notty β€” do not use terminal colors on output
  • --isatty β€” use terminal colors on output β€” useful when running with nohup

πŸ” Packet trace options πŸ”

  • --createtraces β€” create a packet trace for each test
  • --tbsize=TBSIZE β€” capture buffer size for tcpdump [default: 192k]
  • --trcdelay=TRCDELAY β€” seconds to delay before stopping packet trace [default: 2.0]
  • --keeptraces β€” do not remove any trace files [default: remove trace files if no errors]
  • --rmtraces β€” remove trace files [default: remove trace files if no errors]
  • -i INTERFACE, --interface=INTERFACE β€” device interface [default: automatically selected]

πŸŽ€ File options πŸŽ€

  • --nfiles=NFILES β€” number of files to create [default: 2]
  • --filesize=FILESIZE β€” file size to use for test files [default: 64k]
  • --rsize=RSIZE β€” read size to use when reading files [default: 4k]
  • --wsize=WSIZE β€” write size to use when writing files [default: 4k]
  • --iodelay=IODELAY β€” seconds to delay I/O operations [default: 0.1]
  • --offset-delta=OFFSET_DELTA β€” read/write offset delta [default: 4k]

🧚 Path options 🧚

  • --sudo=SUDO β€” full path of binary for sudo [default: '/usr/bin/sudo']
  • --kill=KILL β€” full path of binary for kill [default: '/usr/bin/kill']
  • --nfsstat=NFSSTAT β€” full path of binary for nfsstat [default: '/usr/sbin/nfsstat']
  • --tcpdump=TCPDUMP β€” full path of binary for tcpdump [default: '/usr/sbin/tcpdump']
  • --iptables=IPTABLES β€” full path of binary for iptables [default: '/usr/sbin/iptables']
  • --messages=MESSAGES β€” full path of log messages file [default: '/var/log/messages']
  • --trcevents=TRCEVENTS β€” full path of tracing events directory [default: '/sys/kernel/debug/tracing/events']
  • --trcpipe=TRCPIPE β€” full path of trace pipe file [default: '/sys/kernel/debug/tracing/trace_pipe']
  • --tmpdir=TMPDIR β€” temporary directory [default: '/tmp']

πŸ› Debug options πŸ›

  • --nocleanup β€” do not cleanup created files
  • --notimestamps β€” do not display timestamps in debug messages
  • --bugmsgs=BUGMSGS β€” file containing test messages to mark as bugs if they failed
  • --nomount β€” do not mount server and run the tests on local disk space
  • --basename=BASENAME β€” base name for all files and logs [default: automatically generated]
  • --nfsdebug=NFSDEBUG β€” set NFS kernel debug flags and save log messages [default: '']
  • --rpcdebug=RPCDEBUG β€” set RPC kernel debug flags and save log messages [default: '']
  • --tracepoints=TRACEPOINTS β€” list of trace points modules to enable [default: '']
  • --nfsstats β€” get NFS stats [default: 'False']
  • --pktdisp β€” display main packets related to the given test
  • --nfserrors β€” fail every NFS error found in the packet trace
  • --client-ipaddr=CLIENT_IPADDR β€” IP address of localhost

πŸ“Š Reporting options πŸ“Š

  • --xunit-report β€” generate xUnit compatible test report
  • --xunit-report-file=XUNIT_REPORT_FILE β€” path to xout report file

πŸ§ͺ Test options πŸ§ͺ

  • --runtest=RUNTEST β€” comma separated list of tests to run; if the list starts with a '^' then all tests are run except the ones listed [default: 'all']

πŸ‘‘ TESTS πŸ‘‘

read

verify basic pNFS functionality on a couple of files opened for reading within the same mount. πŸ“–

write

verify basic pNFS functionality on a couple of files opened for writing and then re-opening the first file for writing within the same mount. ✍️

read_write

verify basic pNFS functionality on a couple of files opened for reading and then re-opening the first file for writing within the same mount. πŸ”

write_read

verify basic pNFS functionality on a couple of files opened for writing and then re-opening the first file for reading within the same mount. πŸ”„

read_lock

verify traffic for locked file opened for reading using pNFS. πŸ”’

write_lock

verify traffic for locked file opened for writing using pNFS. πŸ”

setattr

verify setattr traffic for file using pNFS. πŸ’«

setattr_lock

verify setattr traffic for locked file using pNFS. πŸ’«πŸ”’

rw_read

verify traffic for file opened for read and write: reading file first. πŸ“–βž‘οΈβœοΈ

rw_write

verify traffic for file opened for read and write: writing file first. βœοΈβž‘οΈπŸ“–

one_ds

verify client only connects to the DS with I/O. 🎯

rsize

verify traffic for file using pNFS when mount option rsize < 4096. πŸ“

wsize

verify traffic for file using pNFS when mount option wsize < 4096. πŸ“

rwsize

verify traffic for file using pNFS when mount option rsize < 4096 and wsize < 4096. πŸ“πŸ“

nfsvers

verify file created with pNFS is read correctly from different versions of NFS. also, verify files created with different versions of NFS are read correctly from pNFS. 🌐

all

run all tests: read, write, read_write, write_read, read_lock, write_lock, setattr, setattr_lock, rw_read, rw_write, one_ds, rsize, wsize, rwsize, nfsvers. the full lineup bestie, she's doing ALL of it. πŸ†


πŸ“ EXAMPLES πŸ“

the only required option is --server. that's the one thing you can't skip, periodt.

$ nfstest_pnfs --server 192.168.0.11

look at her go. πŸ’…


⚠️ NOTES ⚠️

the user id in the local host must have access to run commands as root using the 'sudo' command without the need for a password. like, it has to just work, no password prompt, no drama. set that up first or she's gonna be stuck at the door. 😭

πŸ’œ SEE ALSO πŸ’œ

formatstr(3), nfstest.test_util(3), nfstest_alloc(1), nfstest_cache(1), nfstest_delegation(1), nfstest_dio(1), nfstest_fcmp(1), nfstest_file(1), nfstest_interop(1), nfstest_io(1), nfstest_lock(1), nfstest_pkt(1), nfstest_posix(1), nfstest_rdma(1), nfstest_sparse(1), nfstest_ssc(1), nfstest_xattr(1), nfstest_xid(1), packet.nfs.nfs4_const(3)

the whole friend group, all linked up. 🫢✨


πŸ’€ BUGS πŸ’€

no known bugs. she said she's flawless and honestly? we believe her. πŸ’…βœ¨


πŸŽ€ AUTHOR πŸŽ€

jorge mora (mora@netapp.com) β€” the legend who wrote her. πŸ‘‘


and that's the whole page bestie!! this is NFStest 3.2, dated 21 March 2023 β€” go run some pNFS tests, you're gonna eat. πŸ½οΈπŸ’–πŸ¦‹ no cap.