From: Steve Dickson <SteveD@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
Kevin Constantine
<Kevin.Constantine-FfNkGbSheRGpB8w63BLUukEOCMrvLtNR@public.gmane.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: nfsstat --sleep=#
Date: Mon, 16 Mar 2009 12:18:30 -0400 [thread overview]
Message-ID: <49BE7BD6.3050303@RedHat.com> (raw)
In-Reply-To: <D5529973-DEFB-4D86-BB94-38EC03517B95@oracle.com>
Chuck Lever wrote:
> On Mar 12, 2009, at Mar 12, 2009, 3:32 PM, J. Bruce Fields wrote:
>> On Thu, Mar 12, 2009 at 01:22:32PM -0400, Chuck Lever wrote:
>>> Actually I would rather see the performance metrics scripts improved.
>>> These tools give a lot more information than nfsstat ever will be able
>>> to.
>>
>> Probably so, but those scripts are a bit hard to find, aren't they?
>>
>> We should
>> - get distributions to install them by default
>> - write man pages?
>> - add references to them where possible (from the nfsstat man
>> page, from howto's/faq's/?)
>
> Steve promised me Red Hat would take care of this when these were added
> to nfs-utils last year.
Not sure what I exactly promised (that's usually not my style 8-) )
but those scripts definitely fell off my radar...
>
>> Until then, unfortunately, improvements to nfsstat are more useful,
>> since nfsstat is the thing people are more likely to run across.
>
> Again, I think improving nfsstat at this point (which is merely for
> compatibility with Solaris) would be wasted work, if we already have
> what is needed in another tool. The Python tools are much more
> sophisticated, and it would be confusing to add their functionality to
> nfsstat (e.g. why can I zero the legacy stats with the -z option, but
> not the stats the come from /proc/self/mountstats?).
>
> Let's spend the effort on the tools that give us deeper results.
I have to agree... I truly think there is a wealth of untapped information
in those mountstats... Just waiting for someone to dip them out...
steved.
next prev parent reply other threads:[~2009-03-16 16:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 1:37 nfsstat --sleep=# Kevin Constantine
[not found] ` <49B86744.6060105-P5ys19MLBK/QT0dZR+AlfA@public.gmane.org>
2009-03-12 1:58 ` Greg Banks
2009-03-12 1:58 ` Kevin Constantine
2009-03-12 14:00 ` Chuck Lever
2009-03-12 15:50 ` J. Bruce Fields
2009-03-12 16:08 ` Chuck Lever
2009-03-12 16:24 ` J. Bruce Fields
2009-03-12 16:34 ` Chuck Lever
2009-03-12 16:45 ` Kevin Constantine
[not found] ` <49B93C10.5020208-P5ys19MLBK/QT0dZR+AlfA@public.gmane.org>
2009-03-12 16:48 ` J. Bruce Fields
2009-03-12 17:09 ` Kevin Constantine
2009-03-12 17:22 ` Chuck Lever
2009-03-12 19:32 ` J. Bruce Fields
2009-03-12 20:24 ` Chuck Lever
2009-03-16 16:18 ` Steve Dickson [this message]
[not found] ` <49BE7BD6.3050303-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-03-16 16:33 ` Chuck Lever
2009-03-12 16:54 ` Chuck Lever
2009-03-12 16:19 ` Greg Banks
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=49BE7BD6.3050303@RedHat.com \
--to=steved@redhat.com \
--cc=Kevin.Constantine-FfNkGbSheRGpB8w63BLUukEOCMrvLtNR@public.gmane.org \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox