On Wed, Jun 22, 2011 at 04:18:52PM +0530, Amit Sahrawat wrote: > Dear All, > ** > *Test Case:13 > * echo " 13. data -> unwritten -> data" > rm -f $testfile > $XFS_IO_PROG $xfs_io_opt -f -c "truncate 20k" \ > -c "$alloc_cmd 0 20k" \ > -c "pwrite 0k 8k" -c "fsync" \ > -c "pwrite 12k 8k" -c "fsync" \ > -c "$zero_cmd 4k 12k" \ > -c "$map_cmd -v" $testfile | $filter_cmd > [ $? -ne 0 ] && die_now > > *After executing individual case like this: > *testfile=/data/usb/sda3/252.testfile > > echo "13. data -> unwritten -> data" > rm -f $testfile > xfs_io -f -c "truncate 20k" -c \ > "falloc 0 20k" -c "pwrite 0k 8k" -c "fsync" -c "pwrite 12k 8k" -c \ > "fsync" -c "fpunch 4k 12k" -c "fiemap -v" $testfile | $filter_cmd > > *Original Output(Taken from 252.out): > * 13. data -> unwritten -> data > 0: [0..7]: data > 1: [8..31]: hole > 2: [32..39]: data > *Output in my case* > 13. data -> unwritten -> data > 0: [0..15]: data > 1: [16..23]: unwritten > 2: [24..39]: data FWIW, it would be much easier for us to understand your problem if you simply posted the output of a failing "check 252" (it's a diff of the output vs the golden output!) rather than a bunch of strange mangled script outputs from whatever wrapper you are using to run xfstests that nobody but you understand. Anyway, I'm pretty sure that 2.6.35.y doesn't support punching holes via the fallocate operation and so this check in the test: _require_xfs_io_falloc_punch is probably not detecting that punch is not supported correctly. Perhaps that is what you need to check first... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
