From: "Michael Stiller" <michael@toyland.ping.de>
To: "Chris Mason" <mason@suse.com>
Cc: "Michael Stiller" <michael@ping.de>,
linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net
Subject: Re: 2.2.19 + reiserfs 3.5.32 nfsd wait_on_buffer/down_failed
Date: 9 May 2001 08:38:23 +0200 [thread overview]
Message-ID: <20010509063824.1424.qmail@toyland.ping.de> (raw)
In-Reply-To: Your message of "Tue, 08 May 2001 22:22:43 EDT." <1164860000.989374963@tiny>
> > 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?
No. Just plain 2.2.19 + reiserfs 3.5.32. Should i use any patches ?
I just checked ftp.suse.com/pub/people/mason/reiserfs/patches and
there are only 2.2.19pre patches.
Does it help to mount the filesystems noatime ?
Chris, do you have any idea where the problem may be located ?
Cheers,
-Michael
--
x(f,s,c)char *s;{return f&1 ? *s ? *s-c ? x(f,++s,c) :7[s]:0:f&2
? x(--f,"!/*,xq-ih9]c$=le&M t)r\nm@p31n%ag.8}Sdoy",c):f&4 ? *s ?
x(f,s+1,putchar(x(f-2,"^&%!*)",*s))) : 0 : 0;}main(){return x(4,
"]!x/mhicn$!iihle&!x/mhiM$agimr%p !r@p%he&!x/mhiM !r@p%he",65);}
prev parent reply other threads:[~2001-05-09 6:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-08 14:42 Michael Stiller
2001-05-09 2:22 ` Chris Mason
2001-05-09 6:38 ` Michael Stiller [this message]
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=20010509063824.1424.qmail@toyland.ping.de \
--to=michael@toyland.ping.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®