From: Dave Chinner <david@fromorbit.com>
To: Roman Kononov <roman@binarylife.net>
Cc: linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: WARNING in xfs_lwr.c, xfs_write()
Date: Sun, 23 May 2010 20:18:56 +1000 [thread overview]
Message-ID: <20100523101856.GL2150@dastard> (raw)
In-Reply-To: <20100523002023.41f5a5c8@aaa.pulp.binarylife.net>
On Sun, May 23, 2010 at 12:20:23AM -0500, Roman Kononov wrote:
> Under some workload, once per ~10 seconds, I'm getting the following warnings
> with 2.6.32.13 and 2.6.33.4 (x86_64). Why are they?
You've got some workload that is mixing direct IO writes with some
form of buffered or mmap IO on the same file and they are racing.
Mixing different types of IO on the one inode is also known as A
Really Bad Idea because there is no guarantee of coherency between
them....
Can you find out what the application is triggering this?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Dave Chinner <david@fromorbit.com>
To: Roman Kononov <roman@binarylife.net>
Cc: xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: WARNING in xfs_lwr.c, xfs_write()
Date: Sun, 23 May 2010 20:18:56 +1000 [thread overview]
Message-ID: <20100523101856.GL2150@dastard> (raw)
In-Reply-To: <20100523002023.41f5a5c8@aaa.pulp.binarylife.net>
On Sun, May 23, 2010 at 12:20:23AM -0500, Roman Kononov wrote:
> Under some workload, once per ~10 seconds, I'm getting the following warnings
> with 2.6.32.13 and 2.6.33.4 (x86_64). Why are they?
You've got some workload that is mixing direct IO writes with some
form of buffered or mmap IO on the same file and they are racing.
Mixing different types of IO on the one inode is also known as A
Really Bad Idea because there is no guarantee of coherency between
them....
Can you find out what the application is triggering this?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2010-05-23 10:16 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-23 5:20 WARNING in xfs_lwr.c, xfs_write() Roman Kononov
2010-05-23 5:20 ` Roman Kononov
2010-05-23 10:18 ` Dave Chinner [this message]
2010-05-23 10:18 ` Dave Chinner
2010-05-23 14:23 ` Roman Kononov
2010-05-23 14:23 ` Roman Kononov
2010-05-24 1:19 ` Dave Chinner
2010-05-24 1:19 ` Dave Chinner
2010-06-12 5:00 ` Ilia Mirkin
2010-06-12 5:00 ` Ilia Mirkin
2010-06-13 22:47 ` Dave Chinner
2010-06-13 22:47 ` Dave Chinner
2010-06-13 23:10 ` Ilia Mirkin
2010-06-13 23:10 ` Ilia Mirkin
2010-06-14 1:29 ` Dave Chinner
2010-06-14 1:29 ` Dave Chinner
2010-06-14 3:27 ` Ilia Mirkin
2010-06-14 3:27 ` Ilia Mirkin
2010-06-14 15:11 ` Roman Kononov
2010-06-14 15:11 ` Roman Kononov
2010-05-24 4:12 ` Stan Hoeppner
2010-05-24 5:16 ` Stewart Smith
2010-05-24 19:34 ` Roman Kononov
2010-05-26 7:06 ` Dave Chinner
2010-05-26 15:07 ` NOW: o_direct -- WAS: " Stan Hoeppner
2010-05-27 11:05 ` Michael Monnerie
2010-05-27 11:47 ` Christoph Hellwig
2010-05-27 13:58 ` Stewart Smith
2010-05-27 14:57 ` Christoph Hellwig
2010-05-27 15:45 ` Stewart Smith
2010-05-28 0:25 ` Stan Hoeppner
2010-05-27 14:05 ` Stewart Smith
2010-05-28 0:42 ` Stan Hoeppner
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=20100523101856.GL2150@dastard \
--to=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roman@binarylife.net \
--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.