From: "G. Allen Morris III" <gam3-nfs@gam3.net>
To: nfs@lists.sourceforge.net
Subject: Re: [RFC] nfsstat v4 layout
Date: Wed, 16 Mar 2005 17:33:27 -0500 [thread overview]
Message-ID: <20050316223327.GA7137@gam3.net> (raw)
In-Reply-To: <20050316173759.GA4360@gam3.net>
On Wed, Mar 16, 2005 at 12:37:59PM -0500, G. Allen Morris III wrote:
>
> I made a patch to nfsstat to display v4 stats.
> I am having a problem with some of the names being so
> long setclientid_confirm for instance.
>
> Is the format below too confusing? Anyone have a better idea?
>
I increased the count to `-8d' and the rows are now 76 charaters
wide. To make them wider I would think about reducing to 5 columns
or making it dynamic (like ls).
I also changed the v4 names to abbreviations.
Allen
--
Server packet stats:
packets udp tcp tcpconn
0 3727 0 0
Server rpc stats:
calls badcalls badauth badclnt xdrcall
3730 0 0 0 0
Server reply cache:
hits misses nocache
0 0 3730
Server file handle cache:
lookup anon ncachedir ncachedir stale
0 0 0 0 1242
Server nfs v2:
null getattr setattr root lookup readlink
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
read wrcache write create remove rename
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
link symlink mkdir rmdir readdir fsstat
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
Server nfs v3:
null getattr setattr lookup access readlink
1 0% 0 0% 0 0% 0 0% 0 0% 0 0%
read write create mkdir symlink mknod
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
remove rmdir rename link readdir readdirplus
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
fsstat fsinfo pathconf commit
3729 99% 0 0% 0 0% 0 0%
Server nfs v4:
null compound
0 0% 0 0%
Client packet stats:
packets udp tcp tcpconn
0 0 0 0
Client rpc stats:
calls retrans authrefrsh
2 0 0
Client nfs v2:
null getattr setattr root lookup readlink
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
read wrcache write create remove rename
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
link symlink mkdir rmdir readdir fsstat
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
Client nfs v3:
null getattr setattr lookup access readlink
0 0% 1 50% 0 0% 0 0% 0 0% 0 0%
read write create mkdir symlink mknod
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
remove rmdir rename link readdir readdirplus
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
fsstat fsinfo pathconf commit
0 0% 1 50% 0 0% 0 0%
Client nfs v4:
null read write commit open open_conf
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
open_noat open_dgrd close setattr fsinfo renew
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
setclntid confirm lock lockt locku access
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
getattr lookup lookup_root remove rename link
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
symlink create pathconf statfs readlink readdir
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
server_caps delegreturn
0 0% 0 0%
-------------------------------------------------------
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-03-16 22:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-16 17:37 [RFC] nfsstat v4 layout G. Allen Morris III
2005-03-16 22:33 ` G. Allen Morris III [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-16 18:05 Lever, Charles
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=20050316223327.GA7137@gam3.net \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox