From: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
To: LKML <linux-kernel@vger.kernel.org>
Subject: 2.5: NFS troubles
Date: 06 Apr 2003 14:06:08 +0200 [thread overview]
Message-ID: <1049630768.592.24.camel@teapot.felipe-alfaro.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1575 bytes --]
Hello,
I'm testing 2.5.66-bk11 on my NFS server running RH9. When I run the
"find" command on the NFS share from my client computer, it hangs
forever after a while, but it always hangs *exactly* at the same place
every time. However, if I boot into NFS with RH9's standard kernel
(2.4.20), the "find" command works as expected and is able to complete
with any hangs or delays.
My NFS server (hostname glass) has a whole ext3 partition - mounted
under /data - formatted as ext3.
/etc/exports is
/data 192.168.0.100(rw,no_root_squash)
/etc/fstab is
/dev/hda3 /data ext3 defaults,noatime 1 2
I have this NFS share placed on my client computer /etc/fstab as
glass:/data /net/glass_data nfs noauto,users,soft 0 0
The client computer is running 2.5.66-mm1. I have attached the following
files, compressed with bzip2 as they are really big:
local-find.bz2 is the result of running the find command locally on the
NFS server (not using NFS) for you to see the whole list of files that
should be shown up.
nfs-find.bz2 is the actual list of files that are shown up using the
find command over the NFS share (running on my client computer) before
the "find" command hangs.
nfs-tcpdump.bz2 is a partial tcpdump output generated while the "find"
command is running over the NFS share.
nfs-strace.bz2 is an "strace -p <pid_of_find_command>" on the find
command that I run on my client computer.
Any ideas on what's hapenning here?
Thank you very much!
________________________________________________________________________
Linux Registered User #287198
[-- Attachment #2: local-find.bz2 --]
[-- Type: application/x-bzip, Size: 15321 bytes --]
[-- Attachment #3: nfs-find.bz2 --]
[-- Type: application/x-bzip, Size: 546 bytes --]
[-- Attachment #4: nfs-strace.bz2 --]
[-- Type: application/x-bzip, Size: 22290 bytes --]
[-- Attachment #5: nfs-tcpdump.bz2 --]
[-- Type: application/x-bzip, Size: 736 bytes --]
next reply other threads:[~2003-04-06 11:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-06 12:06 Felipe Alfaro Solana [this message]
2003-04-06 12:58 ` Trond Myklebust
2003-04-07 0:18 ` Andrew Morton
2003-04-07 0:27 ` Robert Love
2003-04-07 9:01 ` Felipe Alfaro Solana
2003-04-07 9:13 ` Andrew Morton
2003-04-07 9:24 ` Felipe Alfaro Solana
2003-04-07 21:58 ` Trond Myklebust
2003-04-07 9:39 ` Trond Myklebust
2003-04-07 13:23 ` Trond Myklebust
2003-04-07 15:17 ` Robert Love
2003-04-07 8:58 ` Felipe Alfaro Solana
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=1049630768.592.24.camel@teapot.felipe-alfaro.com \
--to=felipe_alfaro@linuxmail.org \
--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
all inboxes | Powered by JetHome®