From: "Malte Schröder" <MalteSch@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: [PROBLEM] [2.6.0-test6] Stale NFS file handle
Date: Sun, 28 Sep 2003 20:30:50 +0200 [thread overview]
Message-ID: <200309282031.54043.MalteSch@gmx.de> (raw)
[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 429 bytes --]
Hi,
since 2.6.0-test6 I get "Stale NFS file handle" when transferring huge amounts
of data from a nfs-server which is running on -test6.
The client also runs -test6. Transfers from a server running kernel 2.4.22
work flawless.
I use the nfs-kernel-server 1.0.6 on Debian/sid.
--
---------------------------------------
Malte Schröder
MalteSch@gmx.de
ICQ# 68121508
---------------------------------------
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-09-28 18:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-28 18:30 Malte Schröder [this message]
2003-09-28 18:48 ` [PROBLEM] [2.6.0-test6] Stale NFS file handle Axel Siebenwirth
2003-09-29 17:42 ` Malte Schröder
2003-09-29 20:06 ` bill davidsen
2003-09-28 20:47 ` Patrick Mau
2003-09-29 18:58 ` Patrick Mau
2003-09-30 4:41 ` Malte Schröder
2003-10-16 5:17 ` Neil Brown
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=200309282031.54043.MalteSch@gmx.de \
--to=maltesch@gmx.de \
--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;
as well as URLs for NNTP newsgroup(s).