Hi Dan,
Dan Price wrote:
> Peter's mail about fsstat kstats inspired me to write up some thoughts
> I have about fsstat. I've been playing with it over the weekend and
> some more today.
>
> 1. Thank God (or thank Rich) that we finally have something in this
> space. It's a vast vast improvement.
:-)
> 2. I'd like to see many more ways to slice the data:
>
> fsstat -A Show all mount points for all FS's
> fsstat -z Skip zero'd entries (like iostat -xz)
> fsstat -a -F <fs> Show all mount points for this FS type
>
> fsstat -a -l Show only local filesystems (no NFS, etc).
> fsstat -a -s Show only non-synthetic filesystems
> (no lofs, mntfs, autofs)
>
> fsstat -Z Aggregate each zone's FS activity
> fsstat -z Watch a particular zone
> (of course I'm proposing two -z's... we'll
> need to work that out :p)
Good ideas, all. Some of these match other suggestions which is good
to hear. I'm not sure (yet) how to separate out the zones part, but I'm
sure we'll be talking. ;-)
> 3. I find the output on the challeging side to visually grok:
>
...
>
> Where does one second end and the next begin? Some spacing or repeating
> the titles or something would help a lot. mpstat and friends all do that;
> this code seems to do it on every third iteration, which I think isn't
> that useful.
It prints the header after every 24(-ish) lines of output. I'm looking
forward to hearing how this gets used so the output can be polished up.
BTW, For easier reading (and date/time correlation) try:
fsstat -T d {interval}
> 4. I'm not sure that the default output is the one which most admins
> would want at a glance. Just my $0.0002.
This part was challenging. The idea was to give an overview of what was
happening on the system. (Separating out the set/get attr ops can be
useful for NFS server/client observability which is what gave birth to
this idea.)
As for the last column: I debated on that... I went for more data.
> I *think* I want the 'fsstat -a -s' output I propose above.
> Correlated with this is the problem that the rightmost column is too
> narrow; I'd consider sacrificing one or merging two columns to get
> some more room on the right for the mount point. Put it together,
> I'd like something like this:
>
> new name attr lookup rddir read read write write
> file ops ops ops ops ops bytes ops bytes
> 2.15K 582 188K 801K 2.90K 189K 230M 7.25K 7.07M /
> 30 37 124 129 0 15 436 16 852 /tmp
> 53 12 471 806 0 176 43.7K 13 2.56K /var/run
> 0 0 0 0 0 0 0 0 0 /mypool
> 6 0 232 150 96 1.71K 168K 5.86K 78.8K /home/dp
> 0 0 3 4 0 0 0 0 0 /home/kg
> 0 0 4 3 2 0 0 0 0 /opt/SUNWspro.40
> 2.95K 2.37K 14 3.88K 0 33.4K 33.4M 35.8K 30.9M /etc/svc/volatile
>
> Thanks again for a very useful tool.
>
Thanks, I appreciate the feedback.
Rich
