xfs
[Top] [All Lists]

Re: XFS Test Case:252 - Shows Wrong Output

To: Amit Sahrawat <amit.sahrawat83@xxxxxxxxx>
Subject: Re: XFS Test Case:252 - Shows Wrong Output
From: Allison Henderson <achender@xxxxxxxxxxxxxxxxxx>
Date: Wed, 22 Jun 2011 10:22:37 -0700
Cc: xfs@xxxxxxxxxxx
In-reply-to: <BANLkTi=wHAxYuLE33AVsc2rp0eEm5GB40w@xxxxxxxxxxxxxx>
References: <BANLkTinBNa9ox+jDaorBoKdhoQQzTUA58A@xxxxxxxxxxxxxx> <BANLkTi=wHAxYuLE33AVsc2rp0eEm5GB40w@xxxxxxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
On 06/22/2011 03:48 AM, Amit Sahrawat wrote:
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

Hi there,

I believe the -c "fpunch 4k 12k" is supposed to be what puts the hole there. If I run the command you have above, the fiemap should show you a hole. Something like this:

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" somefile

wrote 8192/8192 bytes at offset 0
8 KiB, 2 ops; 0.0000 sec (217.014 MiB/sec and 55555.5556 ops/sec)
wrote 8192/8192 bytes at offset 12288
8 KiB, 2 ops; 0.0000 sec (269.397 MiB/sec and 68965.5172 ops/sec)
somefile:
 EXT: FILE-OFFSET      BLOCK-RANGE      TOTAL FLAGS
   0: [0..7]:          296..303             8   0x0
   1: [8..31]:         hole                24
   2: [32..39]:        328..335             8   0x1

If you do not see the hole there, it could be that your punch hole operation is failing for some reason.

Allison Henderson

<Prev in Thread] Current Thread [Next in Thread>