Home | History | Annotate | Download | only in testscripts
      1 The ReadOnly Bind mount tests, uses the filesystems tests from
      2 the {LTPROOT}/testcases/kernel/fs .
      3 
      4 EXECUTING TESTS
      5 ==================
      6 The tests can be executed through runltp like:
      7 
      8 ./runltp -f fs_readonly
      9 
     10 Following tests are executed when the above is invoked:
     11 
     12 IOGEN & DOIO
     13    |
     14     ----- iogen
     15    |
     16     ----- doio
     17    |
     18     ----- rwtest
     19    |
     20     ----- growfiles
     21 FS_INOD
     22 LINKTEST
     23 OPENFILE
     24 INODE
     25 STREAM
     26 FTEST
     27 LFTEST
     28 WRITETEST.
     29 
     30 IOGEN & DOIO
     31 =============
     32 
     33     This is a pair of programs that does basic I/O operations on a set of files.
     34 The file offset, I/O length, I/O operation, and what open(2) flags are
     35 selected randomly from a pre-defined or commandline given set. All data
     36 written can be verified (this is the usual method).
     37 
     38 RWTest
     39 -----
     40 rwtest is a shell script that is a wrapper of iogen and doio.
     41 
     42 Growfiles
     43 --------
     44 Growfiles will create and truncate files in gradual steps using write and lseek.
     45 The system calls are checked for proper returns.
     46 
     47 FS_INOD
     48 ============
     49 
     50 File system stress - inode allocation/deallocation.
     51 Rapidly creates and deletes files through multiple processes running in the
     52 background.
     53 
     54 
     55 LINKTEST
     56 ===========
     57 
     58 Linktest.pl is a simple test that attempts to create a given number of hard
     59 links and symbolic links to a single file.
     60 
     61 
     62 OPENFILE
     63 ===========
     64 
     65 Create files and open simultaneously.
     66 
     67 INODE
     68 ==================
     69 
     70 Does the File system managment and I/O functions work.
     71 This Construct a directory tree, create files in it, and verify
     72 that this was done as expected. It uses the syscalls mkdir, stat, open
     73 
     74 
     75 STREAM
     76 ============
     77 
     78 Performs different tests on the stream  syscalls.
     79 This uses the syscalls freopen, fopen, mknod, ftell, fwrite, fread,  ferror,
     80 feof, clearerr and fileno.
     81 
     82 FTEST
     83 =========
     84 Tests the file I/O, Inodes.
     85 Uses the syscalls
     86  * lseek, read, write,  truncate, ftruncate, fsync, sync, fstat
     87  * open, close, unlink, chdir, readv, writev, lseek64, llseek
     88 
     89 LFTEST
     90 ==========
     91 
     92 Uses the lseek64.
     93 This writes one buffer at a time and lseeks from the beginning of the file to the
     94 end of the last write position
     95 
     96 
     97 WRITETEST
     98 =============
     99 
    100 This test verifies that writes to disk occur without corruption.
    101 Once done , the file is re-opened, the random number generator
    102 is re-seeded, and the file is verified.
    103 
    104 IOCTL
    105 ========
    106 ( Note: Writing the tests to  include tests on the ioctl system calls.)
    107 
    108