linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Dittmer <j.dittmer@portrix.net>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-kernel@vger.kernel.org
Subject: 'NFS stale file handle' with 2.5
Date: Sat, 12 Jul 2003 22:00:09 +0200	[thread overview]
Message-ID: <3F1068C9.1070900@portrix.net> (raw)

Hi,

I'm experiencing really big problems with nfs on 2.5 - and I'm a bit 
stuck debugging.

Server:
Pentium II SMP Dual Server with Raid5/dm and nfs running 2.5.7[045][-mm]

Clients:
Athlon, same kernels
P3 800, same kernels and 2.4

Problem:
Accessing the nfs shares on the Server gives lots of 'nfs stale file 
handles', making it unusuable. A simple cp from nfs to nfs triggers it 
in a matter of seconds.
The shares are mounted with (hard,intr), that used to work with 2.4.20 
on the server, but I also tried no option, only hard and only soft, 
problem persists. Also I tried to remove nfs_directio from the build and 
only compiled in nfs2, all the same.
Being curious whats wrong I set up an export on the P3 800 and mounted 
it from the athlon (both running 2.5.75-mm1). This seems to work fine 
(just tested for 10 minutes or so, but typically the problem is 
triggered much earlier).
I also tried enabling the VERBOSE_DEBUG define in nfs source. But that 
doesn't give any more information.
Only one line that gets my attention:
NFS: giant filename in readdir (len 0x2f0a0969)

I'm really lost here. What can I try/do to further narrow this down? Any 
specific kernel revision I could try to go back, notice that already 
2.5.70 triggered it. With 2.4 on the server nothing of this happens.
Only thing left is to try booting the server without smp support, but I 
get some 'hde: lost interrupt' messages and it doesn't boot.
Note that I also tried to export a partition not on dm. Filesystem is 
ext3. I also tried the patches you posted some days ago in another thread.

Thanks for any suggestions,

Jan

# grep NFS .config
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
CONFIG_NFS_V4=y
CONFIG_NFS_DIRECTIO=y
CONFIG_NFSD=m
CONFIG_NFSD_V3=y
CONFIG_NFSD_V4=y
CONFIG_NFSD_TCP=y


-- 
Linux rubicon 2.5.75-mm1-jd10 #1 SMP Sat Jul 12 19:40:28 CEST 2003 i686


             reply	other threads:[~2003-07-12 19:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-12 20:00 Jan Dittmer [this message]
2003-07-13  1:25 ` 'NFS stale file handle' with 2.5 Jeff Lightfoot
2003-07-13 21:37 ` Neil Brown
2003-07-15 14:00   ` Jan Dittmer
2003-07-15 15:20   ` Jan Dittmer
2003-07-20  8:26   ` Jan Dittmer

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=3F1068C9.1070900@portrix.net \
    --to=j.dittmer@portrix.net \
    --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;
as well as URLs for NNTP newsgroup(s).