From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFS client woes [kernel 2.4.10]
Date: 30 Sep 2001 21:19:05 +0200 [thread overview]
Message-ID: <shslmiwwkpi.fsf@charged.uio.no> (raw)
In-Reply-To: <20010928220342.A18562@florence.intimate.mysticnet.org.uk>
In-Reply-To: Chris Wilson's message of "Fri, 28 Sep 2001 22:03:42 +0100"
>>>>> " " == Chris Wilson <chris@chris-wilson.co.uk> writes:
> [Please CC me if you have any suggestions.] I'm a bit hazy on
> the details, but the synopsis is:
> NFSv3 filesystems, same problem when mounted from either an
> IRIX 6.5.12m or Linux/i386 2.4.10 server.
> 2.4.7: all files are visible all of the time. 2.4.10: some
> files are invisible to some processes.
> The processes that I have noticed to be affected are the likes
> of netscape, all gtk applications and find; perl globbing and
> its readdir function similarly miss files. OTOH, grep and ls
> function fine.
> I'm not certain [read: no idea] what the connection is between
> the files that do disappear. It does not appear to be simply
> inode related, but those modified by the Linux client do seem
> more vulnerable.
> Unfortunately, I only had time to switch back in an old kernel
> and confirm the issue before leaving work. The diff inside
> fs/nfs appeared small, but so do icebergs. ;)
Known glibc bug. If you had trawled the archives a bit you would have
found it.
Set 32bitclients on the server and apply
http://www.fys.uio.no/~trondmy/src/2.4.10/linux-2.4.10-seekdir.dif
Cheers,
Trond
prev parent reply other threads:[~2001-09-30 19:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-28 21:03 NFS client woes [kernel 2.4.10] Chris Wilson
2001-09-30 19:19 ` Trond Myklebust [this message]
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=shslmiwwkpi.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=chris@chris-wilson.co.uk \
--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