From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Andrew Morton <akpm@osdl.org>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: NFS problems with 2.6.4-rc1-mm2
Date: Sat, 06 Mar 2004 12:10:54 +0100 [thread overview]
Message-ID: <1078571454.3811.3.camel@twins> (raw)
In-Reply-To: <20040305143727.5397d76e.akpm@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 1032 bytes --]
The bad guy is:
nfs-tunable-rpc-slot-table.patch
without that patch nfs works fine for me.
As said I use NFSv3 over TCP, and its a SMP machine
that has the problem, I haven't tried any UP box.
Peter
On Fri, 2004-03-05 at 23:37, Andrew Morton wrote:
> Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> >
> > I played about a bit and it's in one of these patches:
> >
> > #nfs-remove-XID-spinlock.patch
> > #nfs-misc-rpc-fixes.patch
> > #nfs-improved-writeback-strategy.patch
> > #nfs-simplify-config-options.patch
> > #nfs-fix-msync.patch
> > #nfs-mount-return-useful-errors.patch
> > #nfs-misc-minor-fixes.patch
> > #nfs-lockd-sync-01.patch
> > #nfs-lockd-sync-02.patch
> > #nfs-lockd-sync-03.patch
> > #nfs-lockd-sync-04.patch
> > #nfs-rpc-remove-redundant-memset.patch
> > #nfs-tunable-rpc-slot-table.patch
> > #nfs-short-read-fix.patch
> >
> > I'll do a binary search through these patches and report those that seem
> > to cause the problem.
>
> Thanks, that would be muchly appreciated.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-03-06 11:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 20:07 NFS problems with 2.6.4-rc1-mm2 Peter Zijlstra
2004-03-05 15:34 ` Peter Zijlstra
[not found] ` <20040305143727.5397d76e.akpm@osdl.org>
2004-03-06 11:10 ` Peter Zijlstra [this message]
2004-03-06 17:16 ` 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=1078571454.3811.3.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--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