From: Amit Sahrawat <amit.sahrawat83@gmail.com>
To: Allison Henderson <achender@linux.vnet.ibm.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS Test Case:252 - Shows Wrong Output
Date: Thu, 23 Jun 2011 11:21:26 +0530 [thread overview]
Message-ID: <BANLkTimuv183W0ef0aYCySWPnv9rLqNuww@mail.gmail.com> (raw)
In-Reply-To: <4E022818.7030406@linux.vnet.ibm.com>
[-- Attachment #1.1: Type: text/plain, Size: 2362 bytes --]
Hi,
*PLATFORM -- Linux/i686 localhost 2.6.31.5-127.fc12.i686.PAE*
The output as per the command mentioned by you:
[root@localhost xfstests-2011-05-11]# xfs_io -f -c "truncate 20k" -c "falloc
0 20k" -c "pwrite 0k 8k" -c "fs
ync" -c "pwrite 12k 8k" -c "fsync" -c "fpunch 4k 12k" -c "fiemap -v"
/media/c/newfile
wrote 8192/8192 bytes at offset 0
8 KiB, 2 ops; 0.0000 sec (434.028 MiB/sec and 111111.1111 ops/sec)
command "fs
ync" not found
wrote 8192/8192 bytes at offset 12288
8 KiB, 2 ops; 0.0000 sec (977 MiB/sec and 250000.0000 ops/sec)
/media/c/newfile:
* EXT: FILE-OFFSET BLOCK-RANGE TOTAL FLAGS
0: [0..15]: 176..191 16 0x0
1: [16..23]: 192..199 8 0x800
2: [24..39]: 200..215 16 0x1
*
Thanks & Regards,
Amit Sahrawat
On Wed, Jun 22, 2011 at 11:06 PM, Allison Henderson <
achender@linux.vnet.ibm.com> wrote:
> On 06/22/2011 03:48 AM, Amit Sahrawat wrote:
>
>> 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
>>
>> Please let me know about the vailidity of this result.
>>
>
> Hi there,
>
> It looks like the "fpunch 4k 12k" is supposed to be what puts the hole
> there. If I run the command you have above, the fiemap should show a hole
> 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 (339.674 MiB/sec and 86956.5217 ops/sec)
>
> somefile:
> EXT: FILE-OFFSET BLOCK-RANGE TOTAL FLAGS
> 0: [0..7]: 256..263 8 0x0
>
> 1: [8..31]: hole 24
> 2: [32..39]: 288..295 8 0x1
>
> If you do not see the hole, it could be your punch hole operation is
> failing for some reason.
>
> Allison Henderson
>
>
[-- Attachment #1.2: Type: text/html, Size: 3539 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-06-23 5:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 10:24 XFS Test Case:252 - Shows Wrong Output Amit Sahrawat
2011-06-22 10:48 ` Amit Sahrawat
2011-06-22 17:22 ` Allison Henderson
2011-06-22 17:36 ` Allison Henderson
2011-06-23 5:51 ` Amit Sahrawat [this message]
2011-06-23 6:20 ` Dave Chinner
2011-06-23 6:36 ` Amit Sahrawat
2011-06-23 10:57 ` Amit Sahrawat
2011-06-23 11:30 ` Amit Sahrawat
2011-06-24 7:15 ` Amit Sahrawat
2011-07-14 18:40 ` Alex Elder
2011-06-22 22:57 ` Dave Chinner
2011-06-23 5:47 ` Amit Sahrawat
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BANLkTimuv183W0ef0aYCySWPnv9rLqNuww@mail.gmail.com \
--to=amit.sahrawat83@gmail.com \
--cc=achender@linux.vnet.ibm.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox