From Fedora Project Wiki
2010-02-04 All day #fedora-test-day (webirc)

What to test?

Today's installment of Fedora Test Day will focus on NFS with a focus on NFSv4 default.

Who's available

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...

What's needed to test

How to test?


To test using Rawhide, you may prepare your system using one of the following methods.

  1. Install latest rawhide from a local mirror. Please follow this guidance to use rawhide -- Install from a nearby rawhide mirror.
  2. Or, update to rawhide from Fedora 34. For guidance, refer to Releases/Rawhide#Yum_update_from_official_release
  3. Alternatively, you may download a non-destructive rawhide live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Live images can be found at .
  4. Either way, be sure you are running with at least kernel-2.6.33-0.24.rc5.git1.fc13, linux-firmware-20100106-1.fc13 and nfs-utils-1.2.1-16.fc13

Fedora 12

Testing can be also be performed on Fedora 12 system with only a few changes.

  1. First, be sure you system is fully up to date
    yum update
  2. Finally, edit the file /etc/nfsmount.conf and comment out the line that reads

Test Cases

Basically, NFS can be tested with both server and client on the same machine, and with different bare-metal or virtual systems. Testers will need to setup a NFS server, and run automated NFS testsuites from client systems. In addition, we will use generic filesystem testsuites to exercise NFS filesystem integrity. An important part of the test event is to make sure everything is working properly after we have switched to NFSv4 by default in Fedora 13.

Also, we will test Secure NFS. All the results will be reported to the table below.

  1. QA:Testcase_nfs_connectathon
  2. QA:Testcase_nfs_pynfs
  3. QA:Testcase_nfs_generic
  4. QA:Testcase_nfs_connectathon_secure
  5. QA:Testcase_nfs_generic_secure

Test Results

Construct a table or list to allow testers to post results. Each column should be a test case or configuration, and each row should consist of test results. For example:

User Smolt Profile connectathon pynfs generic-fs connectathon secure generic-fs secure References
User:caiqian Server HW

Client HW

User:mvadkert Server HW

[TODO Client HW]