From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: NFS problems with 2.6.4-rc1-mm2
Date: Fri, 05 Mar 2004 16:34:16 +0100 [thread overview]
Message-ID: <1078500855.3809.12.camel@twins> (raw)
In-Reply-To: <1078430862.3793.5.camel@twins>
[-- Attachment #1: Type: text/plain, Size: 1566 bytes --]
I'm amazed at the total lack of information I managed to put into it ;-)
Its a dual athlon machine, nfs v3 over tcp. nfsd is run on vanilla
2.4.22 and reports no problems. (yes I know I should upgrade that
machine but its not exposed to the outside world).
anyway,. 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.
Peter Zijlstra
On Thu, 2004-03-04 at 21:07, Peter Zijlstra wrote:
> Hi,
>
> I've just build and booted 2.6.4-rc1-mm2, and mounting my NFS exports
> works. however when I try to unzip a file over those mount the process
> freezes over and any other IO to that mount results in more stuck
> processes. SIGKILL will not remove the processes, only reboot will
> manage.
>
> dmesg reports like:
>
> nfs: server 192.168.0.1 not responding, timed out
>
> which is total nonsense, because all other hosts on the network can
> access the exports just fine.
>
> I'm about to back out all nfs patches from the broken-out patch set to
> see what that does for me.
>
> Peter Zijlstra
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-03-05 15:34 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 [this message]
[not found] ` <20040305143727.5397d76e.akpm@osdl.org>
2004-03-06 11:10 ` Peter Zijlstra
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=1078500855.3809.12.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox