I think a better question is: Is this test supported over NFS? I would suggest looking at the testcase source to determine whether or not it makes sense to run over NFS. Depending on the IO operations and verfication methods, it could be meant for running on local storage only.

-robbie

Subrata Modak <subrata@linux.vnet.ibm.com> wrote on 09/28/2007 07:05:49 AM:

> Hi,
> Please see the following problem reported by Supriya:
> rwtest03 is failing when run on a NFS environment.
>
> Is this reproducible?
>     To reproduce this, mount the ltp suite using NFS and run the
> following commands:
> cd /opt/pFVTR/ltp-full-20070731-m64/testcases/kernel/fs/doio
> export PATH=$PATH:/opt/pFVTR-temp/ltp-full-20070731-m64/testcases/bin/
> export LTPROOT=/opt/pFVTR-temp/ltp-full-20070731-m64
> ./rwtest -N rwtest03 -c -i 60s -n 2  -f buffered -s mmread,mmwrite -
> m random -Dv
> 10%25000:mm-buff-$$ 500b:/test/growfiles/msdos/rwtest03%f
>
> The log message she got was this:
> # ./rwtest -N rwtest03 -c -i 60s -n 2  -f buffered -s mmread,mmwrite-m random
> -Dv 10%25000:mm-buff-$$
> 500b:/test/growfiles/msdos/rwtest03%f/opt/pFVTR-temp/ltp-
> full-20070731-m64/testcases/bin/iogen
> -N rwtest03 -i 60s -f buffered -s mmread,mmwrite -m random 25000b:
> mm-buff-17300
> 500b:/test/growfiles/msdos/rwtest03%f |
> /opt/pFVTR-temp/ltp-full-20070731-m64/testcases/bin/doio -N rwtest03-n 2 -k -v
> iogen(rwtest03):  Could not create/open file /test/growfiles/msdos/rwtest03%f:
> No such file or directory (2)
> iogen(rwtest03) warning:  Couldn't create file
> /test/growfiles/msdos/rwtest03%f
> of 256000 bytes
>
> iogen(rwtest03) starting up with the following:
>
> Out-pipe:              stdout
> Iterations:            60 seconds
> Seed:                  17350
> Offset-Mode:           random
> Overlap Flag:          off
> Mintrans:              1           (1 blocks)
> Maxtrans:              131072      (256 blocks)
> O_RAW/O_SSD Multiple:  (Determined by device)
> Syscalls:              mmread mmwrite
> Aio completion types:  none
> Flags:                 buffered
>
> Test Files:  
>
> Path                                          Length    iou   raw iou file
>                                               (bytes) (bytes) (bytes) type
> -----------------------------------------------------------------------------
> /opt/pFVTR-temp/ltp-full-20070731-m64/testcases/kernel/fs/doio/mm-
> buff-17300  
>  12800000       1     512 regular
>
> doio(rwtest03) (17352) 09:55:54
> ---------------------
> *** DATA COMPARISON ERROR ***
> check_file(/opt/pFVTR-temp/ltp-full-20070731-
> m64/testcases/kernel/fs/doio/mm-buff-17300,
> 6811796, 103968, W:17352:cell8:doio*, 19, 0) failed
>
> Comparison fd is 3, with open flags 0
> Corrupt regions follow - unprintable chars are represented as '.'
> -----------------------------------------------------------------
> corrupt bytes starting at file offset 6811796
>     1st 32 expected bytes:  W:17352:cell8:doio*W:17352:cell8
>     1st 32 actual bytes:    ................................
>
> Request number 25
>           fd 4 is file
> /opt/pFVTR-temp/ltp-full-20070731-m64/testcases/kernel/fs/doio/mm-buff-17300 -
> open flags are 02 O_RDWR,
>           write done at file offset 6811796 - pattern is W (0127)
>           number of requests is 1, strides per request is 1
>           i/o byte count = 103968
>           memory alignment is unaligned
>
> syscall:  mmap-write(NULL, 12800000, PROT_WRITE, MAP_SHARED, 4, 0)
>         file is mmaped to: 0x40012600000
>         file-mem=0x40012c7f094, length=103968, buffer=0x10041540
>
>
> doio(rwtest03) (17351) 09:55:54
> ---------------------
> (parent) pid 17352 exited because of data compare errors
> rwtest(rwtest03) : doio reported errors (r=4)
> rwtest03    1  FAIL  :  doio reported errors (r=4)
> rwtest03    1  FAIL  :  Test failed
> ***End Clone Comments***
>
>
> Has anybody observed this behaviour before ??
>
> --Subrata--
>