From: Andreas Behnert <abehn@gmx.net>
To: nfs@lists.sourceforge.net
Subject: Re: high load
Date: Tue, 22 Apr 2003 10:32:08 +0200 [thread overview]
Message-ID: <3EA4FE08.30105@gmx.net> (raw)
In-Reply-To: <20030418194844.GB29491@oppie.phys.uwm.edu>
Phil Garcia wrote:
> Hi,
>
> We've come across a problem that seems related to the interaction
> between NFS and a 3ware 7500-8 running RAID 5 with one hot spare. We
> have a test program that opens a file and then loops, writing up to
> 255 bytes to the file and then sleeping for up to 10 seconds. We run
> around 200 instances of the program simultaneously for about 25
> minutes.
>
> When we run the processes on 200 separate slaves, writing to a
> (reiserfs) directory under the 3ware controller, the load on the
> server shoots up to over 20 and then gradually declines over the next
> 5 minutes or so.
The problem may be caused by ReiserFS:
If you are using kernel 2.2.x and ReiserFS 3.5.x - ReiserFS for
kernel 2.2.x is REALLY broken. We had similar problems here that
ended up in ReiserFS destroying itself, reproducible! Patches
from ftp.namesys.com didn't help at all. At that time ReiserFS
was nothing more than something to play with.
Can't say anything about kernel 2.4.x and ReiserFS 3.6.x - after
the 3.5.x desasters we moved back to ext2 and are now running ext3
with "data=journal" on our NFS servers without a single problem ...
Regards,
Andreas
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-04-22 8:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-18 19:48 high load Phil Garcia
2003-04-22 8:32 ` Andreas Behnert [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-05 9:49 High load Aniruddh Singh
2006-01-05 10:00 ` Con Kolivas
2006-01-05 11:08 ` Aniruddh Singh
2006-01-06 12:36 ` Aniruddh Singh
2006-01-06 12:57 ` Arjan van de Ven
2006-01-06 15:46 ` Aniruddh Singh
2006-01-06 17:37 ` Arjan van de Ven
2006-01-07 5:47 ` Aniruddh Singh
2006-01-07 5:48 ` Randy.Dunlap
2006-01-09 4:35 ` Aniruddh Singh
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=3EA4FE08.30105@gmx.net \
--to=abehn@gmx.net \
--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.