From: Erik Walthinsen <omega@pdxcolo.net>
To: nfs@lists.sourceforge.net
Cc: "Lever, Charles" <Charles.Lever@netapp.com>
Subject: RE: NAS server avalanche overload
Date: Wed, 03 Mar 2004 14:34:20 -0800 [thread overview]
Message-ID: <1078353259.815.53.camel@localhost> (raw)
In-Reply-To: <482A3FA0050D21419C269D13989C61130435DCCB@lavender-fe.eng.netapp.com>
On Wed, 2004-03-03 at 14:20, Lever, Charles wrote:
> careful: greg said "export options" not "mount options."
> what export options are you using on your NFS server?
Hmm, async is specified in /etc/exports. However, in my early testing I
found that there was no discernible performance difference (with
bonnie++ iirc) between setting the exports one way and setting the
client mount option instead. Either one set to sync would cause
performance drops, as expected, but to the same degree.
I can't change either the exports or client mount options for another
month however, until our quarterly downtime.
- Omega
aka Erik Walthinsen
omega@pdxcolo.net
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next parent reply other threads:[~2004-03-03 22:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <482A3FA0050D21419C269D13989C61130435DCCB@lavender-fe.eng.netapp.com>
2004-03-03 22:34 ` Erik Walthinsen [this message]
2004-03-04 2:07 NAS server avalanche overload Lever, Charles
-- strict thread matches above, loose matches on Subject: below --
2004-03-03 8:31 Erik Walthinsen
2004-03-03 22:02 ` Erik Walthinsen
2004-03-04 0:04 ` Greg Banks
2004-03-04 0:20 ` Erik Walthinsen
2004-03-04 1:40 ` Greg Banks
2004-03-04 2:17 ` Trond Myklebust
2004-03-04 4:39 ` Ian Kent
2004-03-04 5:31 ` Erik Walthinsen
2004-03-04 5:47 ` Greg Banks
2004-03-04 14:38 ` Ian Kent
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=1078353259.815.53.camel@localhost \
--to=omega@pdxcolo.net \
--cc=Charles.Lever@netapp.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.