-
-
Notifications
You must be signed in to change notification settings - Fork 439
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cifsiostat not showing rB/s and wB/s #294
Comments
Could it be that SMB 3 statistics file's format has changed from previous versions? |
Can see bytes read and written in /proc/fs/cifs/Stats Resources in use 0 session 0 share reconnects Max requests in flight: 126
|
The format of this file is that expected by |
Mounted the same SMB 3.1.1 share to Ubuntu 20.04/kernel 5.8 and confirmed can see throughput rate stats Filesystem rB/s wB/s rops/s wops/s fo/s fc/s fd/s Filesystem rB/s wB/s rops/s wops/s fo/s fc/s fd/s Could it be RHE8.3/kernel 4.18 and cifsiostat defect? |
I don't know, but anyway it seems quite unlikely that your problem is a cifsiostat bug. |
BTW, is there a roadmap on adding cifs latency on cifsiostat? |
The kernel should provide the needed counters first so that latency can be calculated. And AFAIK these counters don't exist. |
thanks @sysstat |
Environment:
RHEL 8.3 mounts an SMB 3.1.1 share with MSSQL 2019 database located on the share and active SQL workload(queries and update) running on the share.
Problem:
When running cifsiostat, counters rB/s, wB/s, fc/s, fo/s and fd/s are showing zeros even rops/s and wops/s counters are showing CIFS operations.
"cifsiostat 1" output
Filesystem rB/s wB/s rops/s wops/s fo/s fc/s fd/s
\rhel-smb.io\smb-vol-2 0.00 0.00 33316.00 273.00 0.00 0.00 0.00
Filesystem rB/s wB/s rops/s wops/s fo/s fc/s fd/s
\rhel-smb.io\smb-vol-2 0.00 0.00 32607.00 357.00 0.00 0.00 0.00
Any suggestions on how we display rB/s, wB/s, fc/s, fo/s and fd/s counter stats? Also, is there an option in cifsiostat to show the CIFS latency (just like nfsiostat reporting IOPs and latency)?
The text was updated successfully, but these errors were encountered: