public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: trond.myklebust@fys.uio.no
Cc: green@namesys.com, sneakums@zork.net, linux-kernel@vger.kernel.org
Subject: Re: BUG REPORT: kernel nfs between 2.4.19-pre2 (server) and 2.2.21-pre3 (client)
Date: Fri, 22 Mar 2002 12:00:10 +0100	[thread overview]
Message-ID: <20020322120010.16a53cc9.skraw@ithnet.com> (raw)
In-Reply-To: <15514.30892.392730.325607@charged.uio.no>

On Fri, 22 Mar 2002 01:19:56 +0100
Trond Myklebust <trond.myklebust@fys.uio.no> wrote:

> >>>>> " " == Stephan von Krawczynski <skraw@ithnet.com> writes:
> 
>      > Trond: can you please tell me in short, what the common case
>      > (or your guess) is why I see this stale file handles on the
>      > client side. I am going to try and find out myself what the
>      > problem with reiserfs is here, it gets a bit on my nerves
>      > now. Do you suspect the fs to drop some inodes under the
>      > nfs-server?
> 
> Hold on thar: are you using nfs-server (a.k.a. unfsd) or are you using
> knfsd?

This is a knfsd setup. 

> The client will only return ESTALE if the server has first told it to
> do so. For knfsd, this is only supposed to occur if the file has
> actually been deleted on the server (knfsd is supposed to be able to
> retrieve ReiserFS file that have fallen out of cache).

The files are obviously not deleted from the server. Can you give me a short
hint in where to look after this specific case (source location). I will try to
do some debugging around the place to see what is going on.

Thank you for your help

Stephan


  reply	other threads:[~2002-03-22 11:00 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-09 12:19 BUG REPORT: kernel nfs between 2.4.19-pre2 (server) and 2.2.21-pre3 (client) Stephan von Krawczynski
2002-03-09 19:10 ` Alan Cox
2002-03-10 17:50   ` Stephan von Krawczynski
2002-03-10 22:39 ` Trond Myklebust
2002-03-11  0:18   ` Stephan von Krawczynski
2002-03-11  0:28     ` Trond Myklebust
2002-03-11  6:14       ` Oleg Drokin
2002-03-11 10:46         ` Stephan von Krawczynski
2002-03-11 10:52           ` Oleg Drokin
2002-03-11 11:00             ` Stephan von Krawczynski
2002-03-11 11:11               ` Oleg Drokin
2002-03-11 11:24                 ` Stephan von Krawczynski
2002-03-11 12:47                 ` Stephan von Krawczynski
2002-03-11 12:59                   ` Oleg Drokin
2002-03-11 14:48                     ` Stephan von Krawczynski
2002-03-11 13:51                       ` Oleg Drokin
2002-03-11 13:59                         ` Trond Myklebust
2002-03-11 14:03                           ` Trond Myklebust
2002-03-11 15:57                           ` Stephan von Krawczynski
2002-03-11 16:31                             ` Hans Reiser
2002-03-15 10:32                             ` Oleg Drokin
2002-03-15 11:02                               ` Stephan von Krawczynski
2002-03-15 11:13                                 ` Oleg Drokin
2002-03-15 11:30                                   ` Stephan von Krawczynski
2002-03-15 11:36                                     ` Sean Neakums
2002-03-15 12:03                                       ` Stephan von Krawczynski
2002-03-15 12:05                                         ` Oleg Drokin
2002-03-15 14:07                                           ` Stephan von Krawczynski
2002-03-21 14:45                                           ` Stephan von Krawczynski
2002-03-21 14:57                                             ` Stephan von Krawczynski
2002-03-21 15:01                                               ` Oleg Drokin
2002-03-21 15:05                                                 ` Stephan von Krawczynski
2002-03-21 15:07                                                   ` Oleg Drokin
2002-03-21 17:15                                                     ` Stephan von Krawczynski
2002-03-22  5:48                                                       ` Oleg Drokin
2002-03-22  0:19                                             ` Trond Myklebust
2002-03-22 11:00                                               ` Stephan von Krawczynski [this message]
2002-03-22 11:07                                                 ` Trond Myklebust
2002-03-22 13:19                                                   ` Stephan von Krawczynski
2002-03-15 11:37                                     ` Oleg Drokin
2002-03-18  7:07       ` NIIBE Yutaka
2002-03-18  8:15         ` Trond Myklebust
2002-03-18  9:33           ` NIIBE Yutaka
2002-03-18  9:56             ` Trond Myklebust
2002-03-18 23:57               ` NIIBE Yutaka
2002-03-19 14:45                 ` Trond Myklebust
2002-03-20  0:42                   ` NIIBE Yutaka
2002-03-20  8:30                     ` Trond Myklebust
2002-03-19 15:42               ` Ton Hospel
2002-03-19 18:31                 ` BUG REPORT: kernel nfs between 2.4.19-pre2 (server) and Alan Cox
2002-03-19 22:10                 ` BUG REPORT: kernel nfs between 2.4.19-pre2 (server) and 2.2.21-pre3 (client) Trond Myklebust
2002-03-22 10:33                   ` David Woodhouse
2002-03-22 11:03                     ` Trond Myklebust

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=20020322120010.16a53cc9.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=green@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sneakums@zork.net \
    --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