From: Ian Campbell <ijc@hellion.org.uk>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-nfs@vger.kernel.org, Max Kellermann <mk@cm4all.com>,
linux-kernel@vger.kernel.org, gcosta@redhat.com,
Grant Coady <grant_lkml@dodo.com.au>,
"J. Bruce Fields" <bfields@fieldses.org>,
Tom Tucker <tom@opengridcomputing.com>
Subject: Re: [PATCH 0/3] NFS regression in 2.6.26?, "task blocked for more than 120 seconds"
Date: Sat, 06 Dec 2008 12:16:52 +0000 [thread overview]
Message-ID: <1228565812.10856.30.camel@localhost.localdomain> (raw)
In-Reply-To: <1228169383.20370.3.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]
On Mon, 2008-12-01 at 22:09 +0000, Ian Campbell wrote:
> On Sun, 2008-11-30 at 19:17 -0500, Trond Myklebust wrote:
> > Can you see if the following 3 patches help? They're against 2.6.28-rc6,
> > but afaics the problems are pretty much the same on 2.6.26.
>
> Thanks.
>
> The server was actually running 2.6.25.7 but the matching sources have
> since been removed the backports.org so I've reproduce with 2.6.26 and
> now I'll add the patches.
Just a small progress report. Anecdotally I thought that unpatched
2.6.26.7 was worse than 2.6.25.7, mostly because it hung twice in the ~1
day I was running it where previously it was less frequent than once per
day.
With the patched server the client ran OK for 2.5 days then mysteriously
hung, the logs show none of the normal symptoms and my wife reset it
before I got home so I've no real clue what happened but I'm inclined to
think it was unrelated for now. I'll get back to you in a week or so if
the problem hasn't reoccurred.
Ian.
--
Ian Campbell
It's later than you think.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-12-06 12:17 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 12:32 [PATCH] NFS regression in 2.6.26?, "task blocked for more than 120 seconds" Max Kellermann
2008-10-17 14:33 ` Glauber Costa
2008-10-20 6:51 ` Max Kellermann
2008-10-20 7:43 ` Ian Campbell
2008-10-20 13:15 ` Glauber Costa
2008-10-20 14:12 ` Max Kellermann
2008-10-20 14:34 ` Cyrill Gorcunov
2008-10-20 14:21 ` Cyrill Gorcunov
2009-05-22 20:59 ` H. Peter Anvin
2009-05-25 13:12 ` Max Kellermann
2008-10-20 6:27 ` Ian Campbell
2008-11-01 11:45 ` Ian Campbell
2008-11-01 13:41 ` Trond Myklebust
2008-11-02 14:40 ` Ian Campbell
2008-11-07 2:12 ` kenneth johansson
2008-11-04 19:10 ` Ian Campbell
2008-11-25 7:09 ` Ian Campbell
2008-11-25 13:28 ` Trond Myklebust
2008-11-25 13:38 ` Ian Campbell
2008-11-25 13:57 ` Trond Myklebust
2008-11-25 14:04 ` Ian Campbell
2008-11-26 22:12 ` Ian Campbell
2008-12-01 0:17 ` [PATCH 0/3] " Trond Myklebust
2008-12-01 0:18 ` [PATCH 1/3] SUNRPC: Ensure the server closes sockets in a timely fashion Trond Myklebust
2008-12-17 15:27 ` Tom Tucker
2008-12-17 18:08 ` Trond Myklebust
2008-12-17 18:59 ` Tom Tucker
2008-12-01 0:19 ` [PATCH 2/3] SUNRPC: We only need to call svc_delete_xprt() once Trond Myklebust
2008-12-01 0:20 ` [PATCH 3/3] SUNRPC: svc_xprt_enqueue should not refuse to enqueue 'XPT_DEAD' transports Trond Myklebust
2008-12-17 15:35 ` Tom Tucker
2008-12-17 19:07 ` Trond Myklebust
2008-12-23 14:49 ` Tom Tucker
2008-12-23 23:39 ` Tom Tucker
2008-12-01 0:29 ` [PATCH 0/3] NFS regression in 2.6.26?, "task blocked for more than 120 seconds" Trond Myklebust
2008-12-02 15:22 ` Kasparek Tomas
2008-12-02 15:37 ` Trond Myklebust
2008-12-02 16:26 ` Kasparek Tomas
2008-12-02 18:10 ` Trond Myklebust
2008-12-01 22:09 ` Ian Campbell
2008-12-06 12:16 ` Ian Campbell [this message]
2008-12-14 18:24 ` Ian Campbell
2008-12-16 17:55 ` J. Bruce Fields
2008-12-16 18:39 ` Ian Campbell
2009-01-07 22:21 ` J. Bruce Fields
2009-01-08 18:20 ` J. Bruce Fields
2009-01-08 21:22 ` Ian Campbell
2009-01-08 21:26 ` J. Bruce Fields
2009-01-12 9:46 ` Ian Campbell
2009-01-22 8:27 ` Ian Campbell
2009-01-22 16:44 ` J. Bruce Fields
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=1228565812.10856.30.camel@localhost.localdomain \
--to=ijc@hellion.org.uk \
--cc=bfields@fieldses.org \
--cc=gcosta@redhat.com \
--cc=grant_lkml@dodo.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mk@cm4all.com \
--cc=tom@opengridcomputing.com \
--cc=trond.myklebust@fys.uio.no \
/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