<!-- Copyright (c) 2000, 2001, 2002, 2003, 2004, 2005, 2008, 2009, 2013 The President and Fellows of Harvard College. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE UNIVERSITY AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE UNIVERSITY OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. --> <html> <head> <title>dirconc</title> <body bgcolor=#ffffff> <h2 align=center>dirconc</h2> <h4 align=center>OS/161 Reference Manual</h4> <h3>Name</h3> <p> dirconc - concurrent file system test </p> <h3>Synopsis</h3> <p> <tt>/testbin/dirconc</tt> <em>path</em> [<em>randomseed</em>] </p> <h3>Description</h3> <p> <tt>dirconc</tt> does random directory operations from many processes concurrently. This is a fairly difficult stress test as it exercises cross-directory rename. Quite a number of real-world systems have failed to handle it or larger/longer builds of it. </p> <p> It does its work in a subdirectory of <em>path</em>, so you can run it against whatever filesystem you prefer. </p> <p> If your system survives a <tt>dirconc</tt> run, be sure to check the integrity of the filesystem as well. It's not uncommon for <tt>dirconc</tt> to provoke filesystem corruption. </p> <h3>Requirements</h3> <p> <tt>dirconc</tt> uses the following system calls: <ul> <li> <A HREF=../syscall/getpid.html>getpid</A> <li> <A HREF=../syscall/fork.html>fork</A> <li> <A HREF=../syscall/waitpid.html>waitpid</A> <li> <A HREF=../syscall/mkdir.html>mkdir</A> <li> <A HREF=../syscall/rmdir.html>rmdir</A> <li> <A HREF=../syscall/chdir.html>chdir</A> <li> <A HREF=../syscall/rename.html>rename</A> <li> <A HREF=../syscall/write.html>write</A> <li> <A HREF=../syscall/_exit.html>_exit</A> </ul> </p> <p> <tt>dirconc</tt> should work properly on SFS once the file system assignment is complete. It won't do much of interest on emufs, however. </p> </body> </html>