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