From Fedora Project Wiki

No edit summary
No edit summary
Line 3: Line 3:


|actions=
|actions=
# You can run both NFS server and client on the same system or use different systems. Configure the server.
You can run both NFS server and client on the same system or use different systems. Configure the server.
# Export a NFS mount.
#: <pre>
#: <pre>
#: cp /etc/exports /etc/exports.orig
#: cp /etc/exports /etc/exports.orig
Line 9: Line 10:
#: mkdir /nfs
#: mkdir /nfs
#: service nfs restart</pre>
#: service nfs restart</pre>
# Create test trees.
#: <pre>
#: git clone git://fedorapeople.org/~steved/cthon04
#: cd cthon04
#: ./runcthon --mkdirs /nfs</pre>
From the client,
# Download the connectathon testsuite from the client.
# Download the connectathon testsuite from the client.
#: <pre>
#: <pre>
Line 16: Line 24:
#: cd cthon04
#: cd cthon04
#: make
#: make
#: ./runcthon --server <server IP> --serverdir /nfs </pre>
#: ./runcthon --server <server IP> --serverdir /nfs --onlyv4</pre>


|results=
|results=

Revision as of 09:56, 3 February 2010

Description

This test case is to run connectathon test suite on a NFSv4 root


How to test

You can run both NFS server and client on the same system or use different systems. Configure the server.

  1. Export a NFS mount.
    cp /etc/exports /etc/exports.orig
    echo '/nfs *(rw,insecure,no_root_squash)' > /etc/exports
    mkdir /nfs
    service nfs restart
  2. Create test trees.
    git clone git://fedorapeople.org/~steved/cthon04
    cd cthon04
    ./runcthon --mkdirs /nfs

From the client,

  1. Download the connectathon testsuite from the client.
    git clone git://fedorapeople.org/~steved/cthon04
  2. Run the connectathon testsuite from the client.
    cd cthon04
    make
    ./runcthon --server <server IP> --serverdir /nfs --onlyv4

Expected Results

  1. Step #1 completes without error.
  2. The testsuite finishes without error; no nfs*.error files in /tmp.