Tests performed
NFSv4 is stressed using fsstress in various configurations, exactly in same conditions than with kernel 2.6.11-CITI_NFS4_ALL-3, but we are now using the CITI_NFS4_ALL-5 patches.
Test one : fstress:
fsstress is run in various configurations and parameters
Tests are done with various number of subprocess : 1, 2, 4, 8, 16, 32
Tests are done with a various lenth of instructions lists: 1, 2, 4, 8, 16, 32, 64, 128
Test two:
Run dd if=/dev/zero of=/mnt/nfs/fichier_test one hour
Conclusion
Test one : fstress:
No changes from CITI_NFS4_ALL-3.
Test two:
Issue looks to be fixed. We can kill properly the dd process and umount the NFS filesystem.
The fichier_test file is growing up to 30.109.536.256b. (no space left on device error.
Software configuration
- Server :
- Export options are :
/export
<world>(rw,wdelay,insecure,no_root_squash,no_subtree_check,fsid=0)
- mount options, NFSv4 :
rsize=32768,wsize=32768,timeo=14,intr,noauto
- fsstress -l 0 -d /mnt/benchs_nfs/tmp/ -n <operation_sequence_lenght> -p
<number_of_process> -r
- Linux 2.6.11-CITI_NFS4_ALL-1
hardware configuration
Client
- 2 processors : Intel(R)
- Xeon(TM) CPU 2.80GHz, cache 512 KB
- Total memory: 2Gb
- Ethernet: 1Gb/s link
- Distribution : modified Fedora Core 2
Server
- 4 processors : Intel(R) Xeon(TM) CPU 2.80GHz, cache 512 KB
- Total memory: 24Gb
- Ethernet: 1Gb/s link
- Distribution : modified Fedora Core 2
