linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: green@namesys.com, trond.myklebust@fys.uio.no,
	linux-kernel@vger.kernel.org, neilb@cse.unsw.edu.au
Subject: Re: kernel nfsd
Date: Tue, 18 Mar 2003 17:46:05 +0100	[thread overview]
Message-ID: <20030318174605.7a4820f1.skraw@ithnet.com> (raw)
In-Reply-To: <20030318174106.32065dcb.skraw@ithnet.com>

On Tue, 18 Mar 2003 17:41:06 +0100
Stephan von Krawczynski <skraw@ithnet.com> wrote:

> On Tue, 18 Mar 2003 17:28:25 +0100
> Stephan von Krawczynski <skraw@ithnet.com> wrote:
> 
> > On Tue, 18 Mar 2003 19:07:33 +0300
> > Oleg Drokin <green@namesys.com> wrote:
> > 
> > > Hello!
> > > 
> > > On Tue, Mar 18, 2003 at 04:42:04PM +0100, Stephan von Krawczynski wrote:
> > > 
> > > > > The comment in the code just above the printk() reads
> > > > >                 /* Now that IS odd.  I wonder what it means... */
> > > > > Looks like you and Neil (and possibly the ReiserFS team) might want to
> > > > > have a chat...
> > > > I'm all for it. Who has a glue? I have in fact tons of these messages, it's
> > > > a pretty large nfs server.
> > > 
> > > What is the typical usage pattern for files whose names are printed?
> > > Are they created/deleted often by multiple clients/processes by any chance?
> > 
> > This is a nfs-server who serves web-servers (apache). I find a lot of these
> > messages, but they (upto now) only point to 3 different filenames. And these
> > are in fact all directories. The box never crashed and has currently 20 days
> > uptime. It is dual P-III and has 6 GB of RAM.
> > The questionable directories were created long before they first showed this
> > message and have never changed (regarding name-change). Their contents were
> > possible changed but surely not often meaning no more than once a day or once a
> > week.
> > It may well occur that multiple nfs-client systems _read_ them, as well as
> > multiple processes on one client.
> > The nfs-clients are 2.4.19 boxes and one 2.2.21.
> 
> And one addition:
> They are all second level, meaning look like:

Please ignore this rather silly comment. One should read code before commenting ;-)

-- 
Regards,
Stephan


  reply	other threads:[~2003-03-18 16:35 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-18 14:57 kernel nfsd Stephan von Krawczynski
2003-03-18 15:31 ` Trond Myklebust
2003-03-18 15:42   ` Stephan von Krawczynski
2003-03-18 16:07     ` Oleg Drokin
2003-03-18 16:28       ` Stephan von Krawczynski
2003-03-18 16:41         ` Stephan von Krawczynski
2003-03-18 16:46           ` Stephan von Krawczynski [this message]
2003-03-18 17:28       ` Bernd Schubert
2003-03-19  6:43         ` Oleg Drokin
2003-03-19 11:51           ` Bernd Schubert
2003-03-18 22:09     ` Neil Brown
2003-03-19 11:01       ` Stephan von Krawczynski
2003-03-20 16:22 ` [BUG] nfs client stuck in D state in linux 2.4.17 - 2.4.21-pre5 Vladimir Serov
2003-03-20 16:29   ` Trond Myklebust
2003-03-21  9:31     ` Vladimir Serov
2003-03-21 11:16       ` Trond Myklebust
     [not found]         ` <3E7B0051.8060603@infratel.com>
     [not found]           ` <15995.578.341176.325238@charged.uio.no>
     [not found]             ` <3E7B10DF.5070005@infratel.com>
     [not found]               ` <15995.5996.446164.746224@charged.uio.no>
     [not found]                 ` <3E7B1DF9.2090401@infratel.com>
     [not found]                   ` <15995.10797.983569.410234@charged.uio.no>
2003-05-07 14:42                     ` Vladimir Serov
2003-05-07 15:06                       ` Trond Myklebust
2003-05-08 13:15                         ` Vladimir Serov
2003-05-13 21:11                           ` Trond Myklebust
2003-05-19 13:20                     ` Vladimir Serov
2003-05-20  2:09                       ` Trond Myklebust
2003-05-20 12:07                         ` Vladimir Serov
2003-05-20 12:34                           ` Trond Myklebust
2003-05-21  9:29                       ` Russell King
2003-05-21  9:43                         ` Russell King
2003-05-21 14:58                           ` Nicolas Pitre
2003-05-21 13:36                         ` Vladimir Serov

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=20030318174605.7a4820f1.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=green@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    --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;
as well as URLs for NNTP newsgroup(s).