From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Rince <rincebrain@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: NFS BUG_ON in nfs_do_writepage
Date: Fri, 24 Apr 2009 10:14:19 -0400 [thread overview]
Message-ID: <1240582459.4946.31.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <5da0588e0904240226j3454941y5f58c17a32a9a23d@mail.gmail.com>
On Fri, 2009-04-24 at 05:26 -0400, Rince wrote:
> Applied try 3 of Nick Piggin's patch to 2.6.30-rc3 (cleanly, no less!)
>
> Doesn't appear to have helped at all - I received my favorite BUG ON
> write.c:252 just like always, within 24 hours of booting the kernel,
> even.
>
> - Rich
Yes. I'm able to reproduce this bug now. I found that I can trigger it
fairly reliably by running iozone in something like the following
configuration: "iozone -t 32 -r 1k -s 256m -c -D -K -Z -i0 -i8"
I believe it boils down to the problems being discussed in the following
thread:
http://thread.gmane.org/gmane.linux.nfs/26181
Cheers
Trond
next prev parent reply other threads:[~2009-04-24 14:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 5:46 rercola
2009-04-13 6:50 ` Andrew Morton
2009-04-13 19:16 ` Trond Myklebust
2009-04-13 22:06 ` Rince
2009-04-13 23:44 ` Rince
2009-04-24 9:26 ` Rince
2009-04-24 14:14 ` Trond Myklebust [this message]
2009-04-25 14:57 ` Trond Myklebust
2009-04-26 6:40 ` Nick Piggin
2009-04-26 14:18 ` Trond Myklebust
2009-04-26 15:13 ` Nick Piggin
2009-04-26 17:55 ` Trond Myklebust
2009-04-28 4:27 ` Nick Piggin
2009-04-28 11:45 ` Trond Myklebust
2009-04-28 11:54 ` Nick Piggin
2009-04-28 11:59 ` Trond Myklebust
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=1240582459.4946.31.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=rincebrain@gmail.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
all inboxes | Powered by JetHome®