From: "J. Bruce Fields" <bfields@fieldses.org>
To: Iordan Iordanov <iordan@cdf.toronto.edu>
Cc: linux-nfs@vger.kernel.org
Subject: Re: NFS v3 hangs with kernel version v3.2.0, 32-bit
Date: Thu, 28 Feb 2013 12:29:16 -0500 [thread overview]
Message-ID: <20130228172916.GA29852@fieldses.org> (raw)
In-Reply-To: <512F84AC.1020705@cdf.toronto.edu>
On Thu, Feb 28, 2013 at 11:24:12AM -0500, Iordan Iordanov wrote:
> Hi Bruce,
>
> On 02/22/13 10:01, J. Bruce Fields wrote:
> >Some of that debugging is extremely verbose, yes.
> >
> >Since this list is for upstream (not ubuntu) development, most useful
> >would probably be if you could work out whether the problem is
> >reproduceable on the latest upstream kernel.
>
> Understandable.
>
> We've been unable to pin down what triggers this bug, so we are
> unable to reproduce it synthetically. It only appears to happen on
> shared servers with lots of NFS traffic, and in all cases it
> happened with more than a month of uptime. Also, we are unable to
> put an upstream kernel on a production machine.
>
> These two conditions will make it exceedingly unlikely that we would
> be able to work this out with an upstream kernel.
>
> Even if we were able to reproduce this with an upstream kernel, if
> it takes such a long time to reproduce could that have aged the
> kernel we're testing enough to invalidate our testing results?
Yes, it's certainly harder to know what to do with a fix that can't be
confirmed for months.
But there's certainly no harm in continuing to report any further
symptoms; eventually somebody may recognize the problem.
--b.
prev parent reply other threads:[~2013-02-28 17:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 20:45 NFS v3 hangs with kernel version v3.2.0, 32-bit Iordan Iordanov
2013-02-20 21:25 ` Iordan Iordanov
2013-02-22 15:01 ` J. Bruce Fields
2013-02-28 16:24 ` Iordan Iordanov
2013-02-28 17:29 ` J. Bruce Fields [this message]
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=20130228172916.GA29852@fieldses.org \
--to=bfields@fieldses.org \
--cc=iordan@cdf.toronto.edu \
--cc=linux-nfs@vger.kernel.org \
/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.