From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: LKML <linux-kernel@vger.kernel.org>
Subject: NFS problems with 2.6.4-rc1-mm2
Date: Thu, 04 Mar 2004 21:07:42 +0100 [thread overview]
Message-ID: <1078430862.3793.5.camel@twins> (raw)
[-- Attachment #1: Type: text/plain, Size: 592 bytes --]
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 reply other threads:[~2004-03-04 20:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 20:07 Peter Zijlstra [this message]
2004-03-05 15:34 ` NFS problems with 2.6.4-rc1-mm2 Peter Zijlstra
[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=1078430862.3793.5.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