From: Chris Mason <mason@suse.com>
To: Michael Stiller <michael@ping.de>, linux-kernel@vger.kernel.org
Cc: nfs@lists.sourceforge.net
Subject: Re: 2.2.19 + reiserfs 3.5.32 nfsd wait_on_buffer/down_failed
Date: Tue, 08 May 2001 22:22:43 -0400 [thread overview]
Message-ID: <1164860000.989374963@tiny> (raw)
In-Reply-To: <20010508164243.A23213@ping.de>
On Tuesday, May 08, 2001 04:42:43 PM +0200 Michael Stiller <michael@ping.de> wrote:
> Hi,
>
> we run a nfs server utilizing 2.2.19 + ReiserFS version 3.5.32 on a
> P 3 550 machine. Disk subsystem is a GDT7518RN using 4 UW disks as raid 5
> device. After upgrading from 2.2.17 + reiserfs to 2.2.19 we experience
> many (very much more than with 2.2.17) problems with our nfs clients
> about 12 (linux). Network ist 100Mbit full duplex / switched.
> I do not think this is network related, cause ping -f doesnt show any
> packet loss.
>
> During not so heavy IO on the exported fs
> one nfsd thread seems to be waiting for the disk:
Are you running any patches to make knfsd deal with the reiserfs iget issues?
-chris
next prev parent reply other threads:[~2001-05-09 2:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-08 14:42 2.2.19 + reiserfs 3.5.32 nfsd wait_on_buffer/down_failed Michael Stiller
2001-05-09 2:22 ` Chris Mason [this message]
2001-05-09 6:38 ` Michael Stiller
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=1164860000.989374963@tiny \
--to=mason@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@ping.de \
--cc=nfs@lists.sourceforge.net \
/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.