From: florin@iucha.net (Florin Iucha)
To: David Ford <david+cert@blue-labs.org>
Cc: linux-kernel@vger.kernel.org,
Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: NFS problems with 2.5.53 on server
Date: Fri, 27 Dec 2002 12:17:27 -0600 [thread overview]
Message-ID: <20021227181727.GA14400@beaver> (raw)
In-Reply-To: <3E0C84FC.1020100@blue-labs.org>
[-- Attachment #1: Type: text/plain, Size: 1876 bytes --]
On Fri, Dec 27, 2002 at 11:51:08AM -0500, David Ford wrote:
> Actually I have a bit more information. Using both 2.5.5x (on NFS
> server) and 2.4.19/20, I get in dmesg, "kernel: RPC: garbage, exit EIO"
> and df reports zeroes across the board for NFS volumes.
>
> Nothing fixes it, the NFS server has to be rebooted. During one of
> these moments, I also noticed the NFS server had a non-fatal OOPS w/
> rpc.kmountd. Unfortunately I didn't save the OOPS.
This must be another problem, because I do not see the same problems as
you are seeing. There are no "RPC: garbage" messages and
florin@bear:~$ df | grep archives
beaver:/var/cache/apt/archives 995104 257560 737544 26% /var/autofs/iucha/archives
shows the proper values.
> >I have:
> > bear:/var/cache/apt/archives# mount | grep archives
> > beaver:/var/cache/apt/archives on /var/autofs/iucha/archives type nfs (rw,rsize=8192,wsize=8192,addr=10.10.0.10)
> >Then:
> > bear:/var/cache/apt/archives# ls vim*
> > ls: vim*: No such file or directory
> > bear:/var/cache/apt/archives# find . -name vim\*
> > bear:/var/cache/apt/archives# md5sum vim-gtk_1%3a6.1-266+1_i386.deb
> > 11a6d8dbfb51688d7ac275562540c327 vim-gtk_1%3a6.1-266+1_i386.deb
> > bear:/var/cache/apt/archives#
> >
> >Note that /var/cache/apt/archives is a symbolic link to /var/autofs/iucha/archives.
> >
> >So "ls", "find" cannot find the name for the file, but if I know the
> >file I can open it just fine.
> >
> >On the client:
> > bear:/var/cache/apt/archives# ls | wc -l
> > 91
> >On the server:
> > florin@beaver:/var/cache/apt/archives$ ls | wc -l
> > 441
> >
> >Server has 2.5.53 with no other patches. For clients I have used both 2.5.53
> >and 2.4.19 (Debian package).
Cheers,
florin
--
"NT is to UNIX what a dougnut is to a particle accelerator."
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2002-12-27 18:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-27 16:24 NFS problems with 2.5.53 on server Florin Iucha
2002-12-27 16:51 ` David Ford
2002-12-27 18:17 ` Florin Iucha [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=20021227181727.GA14400@beaver \
--to=florin@iucha.net \
--cc=david+cert@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