All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Steiner <fsteiner-mail@bio.ifi.lmu.de>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Neil Brown <neilb@cse.unsw.edu.au>,
	Kris Vassallo <kris@linuxcertified.com>,
	nfs@lists.sourceforge.net, Olaf Kirch <okir@suse.de>
Subject: Re: Stale File handles keep coming back
Date: Mon, 02 May 2005 08:24:27 +0200	[thread overview]
Message-ID: <4275C79B.5000107@bio.ifi.lmu.de> (raw)
In-Reply-To: <1114878578.14213.6.camel@lade.trondhjem.org>

Trond Myklebust wrote

> On lau , 2005-04-30 at 15:15 +0200, Frank Steiner wrote:
> 
>>reiserfs v3 on both servers (PC and pSeries).
> 
> Is the superblock in reiserfs 3.6 format? What
> does /proc/fs/reiserfs/<partition>/version say?

Hmm, there is not /proc/fs/reiserfs on my system (?), but

debugreiserfs  /dev/mapper/exportraid-home  (yes, LVM)

tells me:

Reiserfs super block in block 16 on 0xfc00 of format 3.6 with standard journal

So I guess that's ok. Also note that the problems wer introduced onlt
after the latest kernel update while the filesystem was created a year
ago and running stable since that time!

I'm currently testing the patch against the acess/getattr flooding that
you sent here because a colleague who is running a few computer pools
observes a correlation between high nfs load and the stale NFS handles.

cu,
Frank


-- 
Dipl.-Inform. Frank Steiner   Web:  http://www.bio.ifi.lmu.de/~steiner/
Lehrstuhl f. Bioinformatik    Mail: http://www.bio.ifi.lmu.de/~steiner/m/
LMU, Amalienstr. 17           Phone: +49 89 2180-4049
80333 Muenchen, Germany       Fax:   +49 89 2180-99-4049
* Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *


-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2005-05-02  6:24 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-25 21:07 Stale File handles keep coming back Kris Vassallo
2005-04-26 12:27 ` Neil Brown
2005-04-26 22:22   ` Kris Vassallo
2005-04-27  2:42     ` Neil Brown
2005-04-29  7:01       ` Frank Steiner
2005-04-29  8:00         ` Frank Steiner
2005-04-29 14:08         ` Trond Myklebust
2005-04-30 13:15           ` Frank Steiner
2005-04-30 16:29             ` Trond Myklebust
2005-05-02  6:24               ` Frank Steiner [this message]
2005-05-03 10:45         ` Frank Steiner
2005-05-03 11:11         ` Frank Steiner
2005-05-05  0:15           ` Kris Vassallo
2005-05-06  6:38             ` Frank Steiner
2005-05-09  6:04               ` Frank Steiner
2005-04-29 14:03       ` Frank Steiner
2005-05-03 21:21   ` Kris Vassallo
2005-05-04  5:44     ` Frank Steiner
2005-05-04 22:48       ` Kris Vassallo
2005-05-04 23:06         ` Trond Myklebust
2005-05-12  1:01       ` Kris Vassallo
2005-05-12  1:14         ` Neil Brown

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=4275C79B.5000107@bio.ifi.lmu.de \
    --to=fsteiner-mail@bio.ifi.lmu.de \
    --cc=kris@linuxcertified.com \
    --cc=neilb@cse.unsw.edu.au \
    --cc=nfs@lists.sourceforge.net \
    --cc=okir@suse.de \
    --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.