From: "J. Bruce Fields" <bfields@fieldses.org>
To: "jehan.procaccia" <jehan.procaccia@int-evry.fr>
Cc: Iozone <capps@iozone.org>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
Jeff Blaine <jblaine@mitre.org>,
nfs@lists.sourceforge.net
Subject: Re: 2.4.21 NFSv3 performance graph
Date: Thu, 17 Feb 2005 11:00:30 -0500 [thread overview]
Message-ID: <20050217160029.GC26738@fieldses.org> (raw)
In-Reply-To: <4214A200.3040206@int-evry.fr>
On Thu, Feb 17, 2005 at 02:54:08PM +0100, jehan.procaccia wrote:
> Hello, I didn't received any answer to the post below ... anyway , I
> finally published my iozone/bonnie++/tar bench here:
> http://www.int-evry.fr/s2ia/user/procacci/Doc/NFS/nfs.html#htoc48
>
> unfortunatly most of them are saturated by the 12.5MB (100Mb) ethernet
> bottle neck, and for the iozone cache suppression I couldn't find a way
> to run corretly with the -U option (which mount/umount FS at every
> tests) because of this error on the nfs server:
> rpc.mountd: refused mount request from arvouin.int-evry.fr for /p2v5f3
> (/p2v5f3): illegal port 34111
>
> I must admit that in the logs I occationnaly get this "illegal port"
> error , even for regular NFS clients (not only iozone testers !) .
> Is this a bug ? a mis configuration ?
It sounds like you just need to add the "insecure" export option to the
relevant export in /etc/exports. See "man exports".
--Bruce Fields
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-02-17 16:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-14 19:00 2.4.21 NFSv3 performance graph Jeff Blaine
2005-01-14 23:59 ` Trond Myklebust
2005-01-18 14:54 ` Jeff Blaine
2005-01-18 17:08 ` Vincent Roqueta
2005-01-21 17:09 ` Jehan PROCACCIA
2005-01-21 17:45 ` Trond Myklebust
2005-01-29 10:48 ` jehan.procaccia
2005-01-29 17:25 ` Iozone
2005-01-30 11:33 ` jehan.procaccia
2005-02-17 13:54 ` jehan.procaccia
2005-02-17 15:44 ` Iozone
2005-02-17 17:27 ` jehan.procaccia
2005-02-17 17:57 ` Iozone
2005-02-17 16:00 ` J. Bruce Fields [this message]
2005-01-29 17:31 ` Iozone
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=20050217160029.GC26738@fieldses.org \
--to=bfields@fieldses.org \
--cc=capps@iozone.org \
--cc=jblaine@mitre.org \
--cc=jehan.procaccia@int-evry.fr \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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.