[Bug testsuite/28958] Current git + RHEL (4.18.0) has 3 working NFSd examples, and one broken.

["bill at broadley dot org" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=28958

--- Comment #7 from BillB <bill at broadley dot org> ---
No, but I could create one.

One of my summaries scripts produces this:

begin=1648245843
end=1648246023

Total ops for 180 seconds

base dir                                          Operations IOPs  IOPS%
Bandwidth bandwidth%
/nas-1-0/abcdefg/home/user99/.schrodinger  7358       40.88 2.30%         0    
 0.00%
/scratch/carsXY.Z9_rsm#z1-14-0-3e/fort.50  4312       23.96 1.35%   1832394    
 1.68%
/scratch/carsXY.Z9_rsm#z8-77-0-99/fort.50  4103       22.79 1.28%   2376893    
 2.18%

hosts:               Operations
   192.168.6.55:31235     37529     11.74%
   192.168.5.51:17155     10623      3.32%
   192.168.13.28:9219      6981      2.18%
   192.168.6.15:57603      6973      2.18%

Operations
  nfsd.proc4.write    146374     45.77%
   nfsd.proc4.read    123553     38.64%
 nfsd.proc4.lookup     20517      6.42%
 nfsd.proc4.commit     19071      5.96%
 nfsd.proc4.remove      7566      2.37%
 nfsd.proc4.rename      2486      0.78%
 nfsd.proc4.create       223      0.07%

I find it great for finding weird behavior, like say the above mentioned file
that's using zero bandwidth, but 40% of the OPS, turns out nearly all are
nfsd.proc4.lookup.  Another common problem is this weird issue where c++
programs seek to X, write 4 byte, seek to X write 8 bytes, seek to X and write
12 bytes .... 4096 bytes, then seek to X+4096.  So only 1 in 1024 writes are
actually kept.

Do scripts like this seem generally useful?

-- 
You are receiving this mail because:
You are the assignee for the bug.