All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ford <david+cert@blue-labs.org>
To: Florin Iucha <florin@iucha.net>, linux-kernel@vger.kernel.org
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: NFS problems with 2.5.53 on server
Date: Fri, 27 Dec 2002 11:51:08 -0500	[thread overview]
Message-ID: <3E0C84FC.1020100@blue-labs.org> (raw)
In-Reply-To: <20021227162426.GA8070@iucha.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

"Ditto"

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.

David

Florin Iucha wrote:

>Hello,
>
>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
>  
>

- -- 
I may have the information you need and I may choose only HTML.  It's up to you. Disclaimer: I am not responsible for any email that you send me nor am I bound to any obligation to deal with any received email in any given fashion.  If you send me spam or a virus, I may in whole or part send you 50,000 return copies of it. I may also publically announce any and all emails and post them to message boards, news sites, and even parody sites.  I may also mark them up, cut and paste, print, and staple them to telephone poles for the enjoyment of people without internet access.  This is not a confidential medium and your assumption that your email can or will be handled confidentially is akin to baring your backside, burying your head in the ground, and thinking nobody can see you butt nekkid and in plain view for miles away.  Don't be a cluebert, buy one from K-mart today.

When it absolutely, positively, has to be destroyed overnight.
                           AIR FORCE

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE+DIT/74cGT/9uvgsRAt7dAKCIzUEq28hVnizmKq4T0cf4h/vm0gCgpL08
2c9VcGcn8ao0A3HMRV/2Qck=
=j4F+
-----END PGP SIGNATURE-----


  reply	other threads:[~2002-12-27 16:43 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 [this message]
2002-12-27 18:17   ` Florin Iucha

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=3E0C84FC.1020100@blue-labs.org \
    --to=david+cert@blue-labs.org \
    --cc=florin@iucha.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.