From: Peng Haitao <penght@cn.fujitsu.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfstests/071 FAIL with pwrite64: Invalid argument
Date: Fri, 06 Jan 2012 11:53:54 +0800 [thread overview]
Message-ID: <4F067052.8080905@cn.fujitsu.com> (raw)
In-Reply-To: <20120104165341.GA21075@infradead.org>
Christoph Hellwig said the following on 2012-1-5 0:53:
> This still fails in my 32-bit test VM:
>
yeah:(
This case will exercise IO at large file with as following condition:
- below upperbound
- upperbound
- above upperbound
But in 32-bit, the case cannot satisfy the condition unless upperbound=16.
When upperbound=16, the case will hung.
The following steps will hung.
# uname -a
Linux Fedora-16-x86 3.1.0-7.fc16.i686.PAE #1 SMP Tue Nov 1 20:53:45 UTC 2011 i686 i686 i386 GNU/Linux
# rpm -q xfsprogs
xfsprogs-3.1.5-1.fc16.i686
# mount /dev/sda10 /sda10/
# xfs_info /dev/sda10
meta-data=/dev/sda10 isize=256 agcount=4, agsize=305088 blks
= sectsz=512 attr=2
data = bsize=4096 blocks=1220352, imaxpct=25
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0
log =internal bsize=4096 blocks=2560, version=2
= sectsz=512 sunit=0 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
# cd /sda10/
# xfs_io -f -c "pwrite 17592186040320 512" tmp
wrote 512/512 bytes at offset 17592186040320
512.000000 bytes, 1 ops; 0.0000 sec (12.850 MiB/sec and 26315.7895 ops/sec)
# xfs_bmap -v tmp
This will hung:(
What is wrong with the steps or xfs wrong?
--
Best Regards,
Peng
> --- 071.out 2009-05-10 16:48:46.000000000 +0000
> +++ 071.out.bad 2012-01-04 16:47:05.000000000 +0000
> @@ -40,14 +40,14 @@
>
>
> Writing 512 bytes, offset is +0 (direct=false)
> -pwrite64: File too large
> +wrote 512/512 bytes at offset <OFFSET>
> Reading 512 bytes (direct=false)
> -read 0/512 bytes at offset <OFFSET>
> +read 512/512 bytes at offset <OFFSET>
>
> and so on
>
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-01-06 3:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 3:42 [PATCH] xfstests/071 FAIL with pwrite64: Invalid argument Peng Haitao
2011-12-06 11:05 ` Dave Chinner
2011-12-06 11:23 ` Christoph Hellwig
2011-12-07 8:17 ` Peng Haitao
2011-12-07 10:07 ` Dave Chinner
2011-12-08 2:25 ` Peng Haitao
2012-01-04 16:53 ` Christoph Hellwig
2012-01-06 3:53 ` Peng Haitao [this message]
2012-03-15 2:25 ` [PATCH v2] " Peng Haitao
2012-03-31 20:13 ` [PATCH v2] 071: make this test work as expected on Linux Christoph Hellwig
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=4F067052.8080905@cn.fujitsu.com \
--to=penght@cn.fujitsu.com \
--cc=hch@infradead.org \
--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