From: Dave Chinner <david@fromorbit.com>
To: Nohez <nohez@cmie.com>
Cc: xfs@oss.sgi.com
Subject: Re: kernel bug in xfs_lrw.c (centos v5.5, directio, aio)
Date: Wed, 18 Aug 2010 21:43:05 +1000 [thread overview]
Message-ID: <20100818114305.GR10429@dastard> (raw)
In-Reply-To: <alpine.LNX.2.00.1008171906220.21398@mahi.cmie.ernet.in>
On Tue, Aug 17, 2010 at 07:12:12PM +0530, Nohez wrote:
>
> Hi,
>
> I had a kernel bug today when running xfs on CentOS v5.5. I moved to
> xfs from ext3 today.
>
> The only application accessing the xfs filesystem is Sybase ASE v15.x.
> Database has been configured to use directio with native kernel
> asynchronous disk i/o enabled.
The warning is being issued because the application is mixing
buffered IO with direct IO on the same file. i.e. data corruption
waiting to happen. This is an application bug - the responsibility
for ensuring data coherency and integrity is assumed by the
application issuing the direct IO.
This was discussed in more detail on a recent thread on this list -
you shoul dbe able to find it in the archives easily enough.
> Let me know if there is any other information I can provide to help
> with debugging.
Report it to the application vendor - it's an application bug, not
a filesystem bug.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-08-18 11:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 13:42 kernel bug in xfs_lrw.c (centos v5.5, directio, aio) Nohez
2010-08-18 11:43 ` Dave Chinner [this message]
2010-08-18 14:51 ` Nohez
2010-08-18 15:55 ` Dave Chinner
2010-08-19 0:47 ` Eric Sandeen
2010-08-19 1:34 ` Dave Chinner
2010-08-19 1:38 ` Eric Sandeen
2010-08-19 1:50 ` 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=20100818114305.GR10429@dastard \
--to=david@fromorbit.com \
--cc=nohez@cmie.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.