From: Greg Banks <gnb@sgi.com>
To: Ian Thurlbeck <ian@stams.strath.ac.uk>
Cc: nfs@lists.sourceforge.net
Subject: Re: Strange delays on NFS server
Date: Wed, 25 Aug 2004 20:02:27 +1000 [thread overview]
Message-ID: <20040825100227.GB16483@sgi.com> (raw)
In-Reply-To: <412C5084.9050605@stams.strath.ac.uk>
On Wed, Aug 25, 2004 at 09:40:36AM +0100, Ian Thurlbeck wrote:
> Server stats since reboot Monday morning. It is lightly
> loaded mostly:
>
> Server nfs v3:
> null getattr setattr lookup access readlink
> 85912 2% 1626277 46% 12375 0% 135833 3% 1295417 36% 773 0%
> read write create mkdir symlink mknod
> 136099 3% 151569 4% 7899 0% 64 0% 194 0% 0 0%
> remove rmdir rename link readdir readdirplus
> 6270 0% 37 0% 2931 0% 969 0% 266 0% 4893 0%
> fsstat fsinfo pathconf commit
> 1508 0% 890 0% 0 0% 41205 1%
Yes, it is lightly loaded. You said your block size is 8K, so
the server has seen about 1.18 GB of writes in 3 days, which is
just over twice RAM size. How many of these slowdown events
did you see in that time?
Can you run "vmstat 1" and log the result please?
You said you have a 3ware RAID controller. What is RAID
configuration, especially RAID level and stripe width? What options
did you use to build the ext3 filesystem?
> So that's about 4 writes for every commit.
Ok, so your clients are doing enough COMMITs.
> File system export:
>
> /export/raid50 @unix(rw,sync,no_wdelay,hide,nocrossmnt,secure,root_squash,
> no_all_squash,subtree_check,secure_locks,mapping=identity,
> anonuid=-2,anongid=-2)
Hmm, no "async". So much for that idea.
Greg.
--
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
I don't speak for SGI.
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-08-25 10:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-11 10:55 Strange delays on NFS server Ian Thurlbeck
2004-08-11 11:58 ` Olaf Kirch
2004-08-11 12:58 ` Steve Dickson
2004-08-11 16:08 ` Ian Thurlbeck
2004-08-11 16:41 ` Olaf Kirch
2004-08-11 16:53 ` Phy Prabab
2004-08-11 16:57 ` Christoph Hellwig
2004-08-11 19:42 ` Norman Weathers
2004-08-12 8:04 ` Ian Thurlbeck
2004-08-12 15:15 ` Ian Thurlbeck
2004-08-13 14:53 ` Steve Dickson
2004-08-16 12:40 ` Ian Thurlbeck
[not found] ` <20040816131434.GL3510@suse.de>
[not found] ` <4120C8D5.3040606@stams.strath.ac.uk>
[not found] ` <20040816145435.GQ3510@suse.de>
[not found] ` <4124CD95.7020007@stams.strath.ac.uk>
[not found] ` <20040820095854.GC23176@suse.de>
2004-08-24 9:48 ` Ian Thurlbeck
2004-08-24 10:27 ` Jan Bruvoll
2004-08-25 2:02 ` Greg Banks
2004-08-25 8:40 ` Ian Thurlbeck
2004-08-25 10:02 ` Greg Banks [this message]
2004-08-25 10:36 ` Ian Thurlbeck
2004-08-24 11:07 ` Neil Brown
2004-08-24 14:22 ` Ian Thurlbeck
2004-08-24 23:54 ` Neil Brown
2004-08-26 11:01 ` Strange delays on NFS server (with piccies) Ian Thurlbeck
2004-08-27 1:22 ` Neil Brown
2004-08-27 4:10 ` Greg Banks
2004-08-11 19:07 ` Strange delays on NFS server Steve Dickson
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=20040825100227.GB16483@sgi.com \
--to=gnb@sgi.com \
--cc=ian@stams.strath.ac.uk \
--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.