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: Thu, 19 Aug 2010 01:55:34 +1000 [thread overview]
Message-ID: <20100818155533.GM7362@dastard> (raw)
In-Reply-To: <alpine.LNX.2.00.1008181715380.12207@sangam.cmie.ernet.in>
On Wed, Aug 18, 2010 at 08:21:31PM +0530, Nohez wrote:
>
> Thank you for your reply.
>
> I checked the archives and found a bug report. The function names in
> the call trace report are different from the ones I have reported.
>
> Since it's an application bug, it does not matter which filesystem
> is being used. Can I assume that the data corruption can happen on
> ext3 too?
It depends on the way the filesystem handles parallelism when doing
direct IO. In general, though, you cannot rely on the filesystem
maintaining data coherence if you mix concurrent buffered/mmap IO
and direct IO to the same file. Filesystems do make efforts to
minimise the possibility of coherency problems, but they cannot be
prevented entirely. Hence the delegation of responsibility to the
application issuing the direct IO.
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 15:55 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
2010-08-18 14:51 ` Nohez
2010-08-18 15:55 ` Dave Chinner [this message]
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=20100818155533.GM7362@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox