From: Eric Sandeen <sandeen@sandeen.net>
To: Ravi Wijayaratne <ravi_wija@yahoo.com>
Cc: xfs@oss.sgi.com
Subject: Re: corruption in xfs_end_bio_unwritten
Date: Tue, 04 Mar 2008 16:15:46 -0600 [thread overview]
Message-ID: <47CDCA12.5060107@sandeen.net> (raw)
In-Reply-To: <629727.55106.qm@web32504.mail.mud.yahoo.com>
Ravi Wijayaratne wrote:
> Hi all,
>
> I am seeing data corruption in xfs_end_bio_unwritten. Possibly the corruption is happening before.
> Here is what I see.
what kernel, for starters?
> The ioend->io_offset and ioend->io_size is completely beyond the range of the size of the file or
> the device altogether. The problem occurs under heavy I/O stress on 4 20GB files that was created
> using XFS_IOC_RESVSP64 ioctl. For a sparse file of the same size the problem does not occur. Also
> the problem is not seen on moderate the low system I/O loads(Created by I/O meter)
>
> It trips on the VOP_BMP(..) call that eventually calls xfs_btree_check_lblock. I am aware that
> this function has changed in the tip to call xfs_iomap_write_unwritten directly instead of calling
> xfs_iomap via VOP_BMAP. I believe that even if I change the code to what is in the tip I would
> still stumble some where on the fact that a write to a undefined range was completed. The call
> stack that was dumped by XFS_ERROR_REPORT was as follows
>
> Any thoughts how I could fix this?
>
> Thanks in advance
>
next prev parent reply other threads:[~2008-03-04 22:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 22:05 corruption in xfs_end_bio_unwritten Ravi Wijayaratne
2008-03-04 22:15 ` Eric Sandeen [this message]
2008-03-05 3:53 ` Eric Sandeen
2008-03-05 7:12 ` 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=47CDCA12.5060107@sandeen.net \
--to=sandeen@sandeen.net \
--cc=ravi_wija@yahoo.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