From: Ian Thurlbeck <ian@stams.strath.ac.uk>
To: Greg Banks <gnb@sgi.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: Strange delays on NFS server
Date: Wed, 25 Aug 2004 11:36:26 +0100 [thread overview]
Message-ID: <412C6BAA.8010900@stams.strath.ac.uk> (raw)
In-Reply-To: <20040825100227.GB16483@sgi.com>
Greg Banks wrote:
> 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?
Well, at least 10 per day, probably more.
> Can you run "vmstat 1" and log the result please?
Not sure what you mean. Quick snapshot follows, but I'll leave it
running and watch what happens during an "event".
procs memory swap io system
cpu
r b swpd free buff cache si so bi bo in cs us
sy wa id
0 0 12248 43816 25148 70164 1 0 141 203 234 102 2
2 0 96
0 0 12248 43804 25148 70168 0 0 0 0 114 82 0
2 0 98
0 0 12248 43772 25180 70168 0 0 0 212 154 125 0
1 0 99
0 0 12248 43772 25180 70168 0 0 0 0 111 82 0
1 0 99
> 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?
Capacity: 247.04 GB (482505216 blocks)
Write Cache: In Use
Configuration: Striped with Parity 64K (RAID 5)
Stripe size: 64K (65536 bytes)
Ext3 options: anyone know what the default is for Fedora Core 1?
Here is output from tune2fs -l:
tune2fs 1.34 (25-Jul-2003)
Filesystem volume name: /spare
Last mounted on: <not available>
Filesystem UUID: 5070c833-cdfe-408b-ae12-ee4587e7ffc4
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal filetype needs_recovery
sparse_super large_file
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 30162944
Block count: 60312018
Reserved block count: 3015600
Free blocks: 34369240
Free inodes: 29320077
First block: 0
Block size: 4096
Fragment size: 4096
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 16384
Inode blocks per group: 512
Filesystem created: Mon May 19 03:28:12 2003
Last mount time: Mon Aug 23 08:45:09 2004
Last write time: Mon Aug 23 08:45:09 2004
Mount count: 31
Maximum mount count: -1
Last checked: Mon May 19 03:28:12 2003
Check interval: 0 (<none>)
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 128
Journal inode: 8
Default directory hash: tea
Directory Hash Seed: e37b261f-2740-4f6c-a970-d4aade2b54be
Ian
>
>>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.
--
Ian Thurlbeck http://www.stams.strath.ac.uk/
Statistics and Modelling Science, University of Strathclyde
Livingstone Tower, 26 Richmond Street, Glasgow, UK, G1 1XH
Tel: +44 (0)141 548 3667 Fax: +44 (0)141 552 2079
-------------------------------------------------------
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:38 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
2004-08-25 10:36 ` Ian Thurlbeck [this message]
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=412C6BAA.8010900@stams.strath.ac.uk \
--to=ian@stams.strath.ac.uk \
--cc=gnb@sgi.com \
--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.