From: "J. Bruce Fields" <bfields@fieldses.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Nick Piggin <npiggin@kernel.dk>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Al Viro <viro@ZenIV.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: Odd NFS related SIGBUS (& possible fix)
Date: Fri, 1 Oct 2010 13:18:10 -0400 [thread overview]
Message-ID: <20101001171810.GC30570@fieldses.org> (raw)
In-Reply-To: <1285912667.2463.68.camel@pasglop>
On Fri, Oct 01, 2010 at 03:57:47PM +1000, Benjamin Herrenschmidt wrote:
> (Reminder: On 2.6.32.16, where we initially experienced the problem, I
> found out that we get a -lot- of invalidations coming due to server
> mtime being more recent than the local mtime, which is very very odd
> considering that the local machine is the only one to ever modify the
> files)
Possibly also related?:
https://bugzilla.redhat.com/show_bug.cgi?id=636590
We see what seem to be cache invalidations when all we're doing is
something like
open
write
close
open
read
from a single thread on a single client. This happens over a variety of
protocol and server versions.
--b.
next prev parent reply other threads:[~2010-10-01 17:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 4:33 Odd NFS related SIGBUS (& possible fix) Benjamin Herrenschmidt
2010-09-29 7:44 ` Benjamin Herrenschmidt
2010-10-01 5:57 ` Benjamin Herrenschmidt
2010-10-01 6:01 ` Benjamin Herrenschmidt
2010-10-01 17:18 ` J. Bruce Fields [this message]
2010-10-01 18:12 ` Trond Myklebust
2010-10-01 18:35 ` Trond Myklebust
2010-10-01 20:57 ` Benjamin Herrenschmidt
2010-10-18 23:43 ` Benjamin Herrenschmidt
2010-10-01 20:53 ` Benjamin Herrenschmidt
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=20101001171810.GC30570@fieldses.org \
--to=bfields@fieldses.org \
--cc=benh@kernel.crashing.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=npiggin@kernel.dk \
--cc=trond.myklebust@fys.uio.no \
--cc=viro@ZenIV.linux.org.uk \
/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