From: David Ford <david+powerix@blue-labs.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
trond.myklebust@fys.uio.no
Subject: NFS problems, 2.5.5x
Date: Fri, 31 Jan 2003 18:13:02 -0800 [thread overview]
Message-ID: <3E3B2D2E.8000604@blue-labs.org> (raw)
Synopsis: nfsserver:/home/david mount, get dir. entries loops forever,
2.5.59 for client and server.
Example: ls -l /home/david
An strace will show the same directory entries flying by over and over
until memory is exhausted or ^c comes along. It worked at first for
about 30 minutes while I finished the new gentoo install on my desktop,
but then things got weird. the nfs server spat out a big long callback
trace (oops) and died hard. Had to reset the power. The looping
started just minutes before that. I've rebooted, tried 2.5.53 on the
client but no go.
Doing a stat on a single file works fine. Doing a glob, i.e. ls -l on
the mount directory fails. Doing ls -l on any sub directory of the
mount works fine.
ls -la /home/david/.xinitrc (file, works)
ls -la /home/david/.e (directory, works)
ls -la /home/david (loops forever on all directory entries until memory
is exhausted and ls aborts)
Some things I've noted:
- not all directory entries are repeated, some only appear once and
never again.
- ls only does this on the mount point of the nfs mounted directory, all
other directories are fine
GLIBC 2.3.1, underlying filesystems are reiserfs.
Client:
nfsserver:/home/david on /home/david type nfs
(rw,bg,hard,intr,timeo=7,rsize=16384,wsize=16384,addr=10.0.0.5)
Server (/var/lib/nfs/etab):
/raid/home/david
hb.blue-labs.org(rw,async,wdelay,hide,secure,no_root_squash,no_all_squash,subtree_check,secure_locks,mapping=identity,anonuid=-2,anongid=-2)
David
next reply other threads:[~2003-02-01 2:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-01 2:13 David Ford [this message]
2003-02-01 2:30 ` NFS problems, 2.5.5x Andrew Morton
2003-02-01 2:46 ` David Ford
2003-02-01 8:58 ` Trond Myklebust
2003-02-01 16:03 ` David Ford
2003-02-01 16:23 ` Trond Myklebust
2003-02-01 21:49 ` David Ford
2003-02-03 11:12 ` Oleg Drokin
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=3E3B2D2E.8000604@blue-labs.org \
--to=david+powerix@blue-labs.org \
--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