Bull GNU/Linux NFSv4 project

Stressing NFSv4

Tests performed

NFSv4 is stressed using fsstress in various configurations, exactly in same conditions than with kernel 2.6.11-CITI_NFS4_ALL-5, but we are now using the linux 2.6.12-rc1-CITI_NFS4_ALL-2 kernel and 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 : fsx

• fsx is run with 5000 iterations (From LTP configuration)

Test three : connectathon

• Client and server are running linux.

Test four

• dd if=/dev/zero of=/mnt/nfs/testfile

Conclusion

Test one : fstress:

• Test run 24 hours with success.

Test one : fsx

• Test run with success.

Test three : connectathon

• Test run with success.

Test four

• Test run with success up to 35GB.(Error: No space left on device)

Core NFSv4 functions should be considered as stable. There is no remaining bug in this version.

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.12-rc1-CITI_NFS4_ALL-2

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

Page maintained by: Vincent Roqueta		Accessed times since its creation.
	Last update: 2005, September 23