All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Dogar <sean@catfeeder.net>
To: "G. Allen Morris III" <gam3-nfs@gam3.net>
Cc: nfs@lists.sourceforge.net
Subject: Re: nhfsstone
Date: Wed, 16 Mar 2005 09:27:56 -0700	[thread overview]
Message-ID: <42385E8C.2060509@catfeeder.net> (raw)
In-Reply-To: <20050316153733.GA19335@gam3.net>

[-- Attachment #1: Type: text/plain, Size: 1239 bytes --]

G. Allen Morris III wrote:

>On Tue, Mar 15, 2005 at 02:03:40PM -0700, Sean Dogar wrote:
>  
>
>>Has anybody used the nfs benchmarking utility "nhfsstone"? 
>>
>>I can run it, and I can see that it's doing work (it makes test 
>>directories in the NFS-mounted directory that I start it from), but it 
>>never finishes it's testing or gives me any performance info.  I've 
>>tried the various options, including a -t 120 (I thought that this would 
>>restrict run-time to 120 seconds) and others, but I still get no output, 
>>even with verbose.  It doesn't send any output to files either.  It just 
>>runs and runs.   This is on a Redhat 8 machine as a client mounting an 
>>AIX NFS export. 
>>
>>The man page is sort of vague, but I get the impression that you can run 
>>it without any arguments, and it will do a test with the various 
>>defaults, and eventually should return. 
>>
>>Does anybody have any idea on this or do you know somewhere to point me 
>>for more info?  Most of the stuff I've found through Google has been the 
>>man page itself. 
>>
>>    
>>
>
>It seems that nhfsstone only benchmarks nfs v2 filesystems.  It is
>likely that you are using v3.
>
>Allen Morris
>  
>
That's exactly what it is...thank you.

-Sean

[-- Attachment #2: Type: text/html, Size: 1625 bytes --]

      reply	other threads:[~2005-03-16 16:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-15 21:03 nhfsstone Sean Dogar
2005-03-16  8:19 ` nhfsstone Denis Vlasenko
2005-03-16 15:37 ` nhfsstone G. Allen Morris III
2005-03-16 16:27   ` Sean Dogar [this message]

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=42385E8C.2060509@catfeeder.net \
    --to=sean@catfeeder.net \
    --cc=gam3-nfs@gam3.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.