From: Christoph Hellwig <hch@lst.de>
To: Ming Lin <mlin@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>, xfs@oss.sgi.com
Subject: Re: xfs_io bmap confused
Date: Wed, 8 Jul 2015 10:53:41 +0200 [thread overview]
Message-ID: <20150708085341.GA23332@lst.de> (raw)
In-Reply-To: <1436338913.13729.11.camel@hasee>
On Wed, Jul 08, 2015 at 12:01:53AM -0700, Ming Lin wrote:
> Hi list,
>
> I am testing some direct-io patches.
> xfs_tests/xfs/080 failed.
>
> It's strange.
> There is no hole in "rwtest.file",
> but when read it at some offset it returns zero because of hole.
>
> root@block:~# xfs_io -c bmap /mnt/test/rwtest.file
> /mnt/test/rwtest.file:
> 0: [0..125671]: 160..125831
Sounds like you see an unwritten extent. What does xfs_bmap -pv show on
the file?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-07-08 8:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 7:01 xfs_io bmap confused Ming Lin
2015-07-08 8:53 ` Christoph Hellwig [this message]
2015-07-08 13:57 ` Ming Lin
2015-07-08 23:40 ` Ming Lin
2015-07-09 6:54 ` Ming Lin
2015-07-09 22:41 ` Dave Chinner
2015-07-09 23:28 ` Ming Lin
2015-07-09 2:07 ` Dave Chinner
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=20150708085341.GA23332@lst.de \
--to=hch@lst.de \
--cc=mlin@kernel.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