Matrix robustness section

From Linux NFS

(Difference between revisions)
Jump to: navigation, search
(→Basic stability assessments)
(→Resource limit testing)
Line 74: Line 74:
== Resource limit testing ==
== Resource limit testing ==
-
 
+
{|border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; text-align: center; width: 100%
-
<table nosave="" border="1" width="85%">
+
!style="background: #ececec;"|'''ID
-
<tr nosave="" align="center" valign="CENTER">
+
!style="background: #ececec;"|'''test'''
-
<td nosave="" align="center" valign="CENTER"></td>
+
!style="background: #ececec;"|'''tool test'''
-
 
+
!style="background: #ececec;"|'''status'''
-
<td>test</td>
+
!style="background: #ececec;"|'''owner'''
-
<td>tool test</td>
+
!style="background: #ececec;"|'''notes'''
-
<td>status</td>
+
|-
-
<td>Owner</td>
+
|III.B.1
-
<td>notes</td>
+
|Test stability of client in out of pid situation
-
</tr>
+
|
-
<tr>
+
|
-
<td>III.B.1</td>
+
|
-
<td>
+
|
-
Test stability of client in out of pid situation</td><td></td><td></td><td></td><td></td>
+
|-
-
</tr>
+
|III.B.2
-
<tr>
+
|Test stability of client in out of memory situation
-
<td>III.B.2</td>
+
|valgrind
-
<td>
+
|'''New'''
-
Test stability of client in out of memory situation</td><td>valgrind</td><td>'''new'''</td><td></td><td>IA32</td>
+
|
-
</tr>
+
|
-
<tr>
+
|-
-
<td>III.B.3</td>
+
|III.B.3
-
<td>
+
|Test stability of client in out of disk space on server situation
-
Test stability of client in out of disk space on server situation</td><td>dd,fsstress</td><td>'''done'''</td><td>BULL</td><td>Simple error message ''no space left on device''</td>
+
|dd,fsstress
-
<tr>
+
|'''Done'''
-
<td>III.B.4</td>
+
|Bull
-
<td>
+
|Simple error message ''no space left on device''
-
Test stability of client in out of inode situation</td><td></td><td></td><td></td><td></td>
+
|-
-
</tr>
+
|III.B.4
-
<tr>
+
|Test stability of client in out of inode situation
-
<td>III.B.5</td>
+
|
-
<td>
+
|
-
Test stability of client in out of swap space situation</td><td></td><td></td><td></td><td></td>
+
|
-
</tr>
+
|
-
<tr>
+
|-
-
<td>III.B.6</td>
+
|III.B.5
-
<td>
+
|Test stability of client in out of swap space situation
-
Test stability of server in out of pid situation</td><td></td><td></td><td></td><td></td>
+
|
-
</tr>
+
|
-
<tr>
+
|
-
<td>III.B.7</td>
+
|
-
<td>
+
|-
-
Test stability of server in out of memory situation</td><td>valgrind</td><td>'''new'''</td><td></td><td>IA32</td>
+
|III.B.6
-
</tr>
+
|Test stability of server in out of pid situation
-
<tr>
+
|
-
<td>III.B.8</td>
+
|
-
<td>
+
|
-
Test stability of server in out of disk space situation</td><td>dd,fsstress</td><td>'''done'''</td><td>BULL</td><td> Simple error message ''no space left on device''</td>
+
|
-
<tr>
+
|-
-
<td>III.B.9</td>
+
|III.B.7
-
<td>
+
|Test stability of server in out of memory situation
-
Test stability of server in out of inode situation</td><td></td><td></td><td></td><td></td>
+
|valgrind
-
</tr>
+
|'''New'''
-
<tr>
+
|
-
<td>III.B.10</td>
+
|
-
<td>
+
|-
-
Test stability of server in out of swap space situation</td><td></td><td></td><td></td><td></td>
+
|III.B.8
-
</tr>
+
|Test stability of server in out of disk space
-
</table>
+
|dd,fsstress
 +
|'''Done'''
 +
|Bull
 +
|Simple error message ''no space left on device''
 +
|-
 +
|III.B.9
 +
|Test stability of server in out of inode situation
 +
|
 +
|
 +
|
 +
|
 +
|-
 +
|III.B.10
 +
|Test stability of server in out of swap space situation
 +
|
 +
|
 +
|
 +
|
 +
|}
==Stress load testing==
==Stress load testing==

Revision as of 12:56, 19 May 2005

Section III

Contents

ROBUSTNESS TESTING

Basic stability assessments

ID test tool test status owner notes
III.A.1 Run iozone for 2 weeks on basic client/server operations, using:
  • Both data and metadata options
  • Cached and direct I/O
  • Various mount options
IOzone done BULL Now testing with fsstress and FFSB
III.A.2 Run automounter use case for 2 weeks on amd, autofs, and autong, using:
  • Large number of maps
  • Randomly mount and run workloads on an automounted partition
  • use a variety of workloads, such as randomly chosen fs tests
e.g. Crashme more New
III.A.3 Run NFS server for 2 wks with random configuration changes, using:
  • Interrupt server in various ways (reboot, power cycle, lan fail)
  • Change/reexport export rules at random
  • Trigger a client workload at arbitrary times
  • Analyze client recovery behaviors
OPEN OSDL
III.A.4 Run connectathon locking tests against NFS server for 2 weeks, using:
  • Multiple client machines
  • Reboot at random
  • Analyze client cache coherency behaviors
  • Analyze locking behaviors
NEW
III.A.5 Run fsstress 2 weeks on basic client/server operations, using:
  • Long list random operations (1000 operations)
  • hight number of process (100)
fsstress DONE BULL 1 week
III.A.6 Run FFSB 1 day on basic client/server operations in stress configuration, using:
  • 1 200 000 files
  • 100 directories
ffsb DONE BULL 1 day

Resource limit testing

ID test tool test status owner notes
III.B.1 Test stability of client in out of pid situation
III.B.2 Test stability of client in out of memory situation valgrind New
III.B.3 Test stability of client in out of disk space on server situation dd,fsstress Done Bull Simple error message no space left on device
III.B.4 Test stability of client in out of inode situation
III.B.5 Test stability of client in out of swap space situation
III.B.6 Test stability of server in out of pid situation
III.B.7 Test stability of server in out of memory situation valgrind New
III.B.8 Test stability of server in out of disk space dd,fsstress Done Bull Simple error message no space left on device
III.B.9 Test stability of server in out of inode situation
III.B.10 Test stability of server in out of swap space situation

Stress load testing

test tool test status Owner notes
III.C.1 Run stress tools in a std config on each release fsx,fsstress,ffsbIn progressBULL Tests used:
  • fsx
  • fsstress (1h)
  • ffsb (1h)
III.C.2 Analyze load balancing, failure modes, etc. under different stress loads New
III.C.3 Destructive testing by measuring point of failure for various loads New

Scalability (robustness)

test tool test status Owner notes
III.D.1 Find maximum number of connections to Linux IA-32 serverFsstress, fsxNewBull (partial)
III.D.2 Find maximum number of files for Linux IA-32 exported file systemNew
III.D.3 Find maximum file size on Linux IA-32New
III.D.4 Find maximum number of mounted file systems on clientFsstress, fsxNewBull
III.D.5 Test robustness on NUMA when scaling CPU, mem, NIC, or disk countFsstress, fsxNew
III.D.6 Test robustness on SMP when scaling CPU, mem, NIC, or disk countFsstress, fsxNewBull (partial)
III.D.7 Test correctness of NFS client when backed by a large (>100GB) cachefsNew
III.D.8 Find maximum number exported file systems on serverNew
III.D.9 Find maximum size of exported file systems on serverNew

Recovery from problems while under light/normal/heavy loads

test tool test status Owner notes
III.E.1 Test short & long term local network failure (unplugged cable, ifdown eth0, etc.)OpenOSDL
III.E.2 Test short & long duration remote network partitionOpenOSDL
III.E.3 Test behavior during crash/reboot of server with clients holding various statesOpenOSDLmore
III.E.4 Test multiple clients using, locking, etc. same filesNew
III.E.5 Test behavior of server with failed storage deviceNew
III.E.6 Test behavior during crash of client with open delegations and locksNew
III.E.7 Test recovery from denied permissionNew
III.E.5 Test recovery from JUKEBOX/DELAYNew
III.E.5 Test recovery from ESTALENew
Retrieved from "http://wiki.linux-nfs.org/wiki/index.php/Matrix_robustness_section"
Personal tools