Skip to content
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

arcstat showing most fields as zero #9698

Closed
aaronjwood opened this issue Dec 8, 2019 · 4 comments
Closed

arcstat showing most fields as zero #9698

aaronjwood opened this issue Dec 8, 2019 · 4 comments
Labels
good first issue Indicates a good issue for first-time contributors Status: Stale No recent activity for issue Type: Regression Indicates a functional regression

Comments

@aaronjwood
Copy link

System information

Type Version/Name
Distribution Name Ubuntu
Distribution Version 19.10
Linux Kernel 5.3.0-23-generic #25-Ubuntu SMP
Architecture x86_64
ZFS Version 0.8.1-1ubuntu14
SPL Version

Describe the problem you're observing

On my system arcstat doesn't seem to work at all. Some examples:

arcstat
    time  read  miss  miss%  dmis  dm%  pmis  pm%  mmis  mm%  arcsz     c
20:43:52     0     0      0     0    0     0    0     0    0    15G   15G
arcstat -x
    time   mfu   mru  mfug  mrug  eskip  mtxmis  dread  pread  read
20:45:45     0     0     0     0      0       0      0      0     0

Describe how to reproduce the problem

Just run arcstat or arcstat -x.

Include any warning/errors/backtraces from the system logs

@Fabian-Gruenbichler
Copy link
Contributor

this is not a bug - you probably want to do "arcstat 30" or some other interval..

@aaronjwood
Copy link
Author

My fault. I was expecting the older behavior from the tool. Passing an interval of 1 shows valid data after 1 second.

Since the first print always shows zeros for most fields would it make sense to not print anything at all until the first iteration of the interval has been reached?

@gmelikov gmelikov added the Type: Regression Indicates a functional regression label Dec 9, 2019
@behlendorf behlendorf added the good first issue Indicates a good issue for first-time contributors label Dec 9, 2019
@johnramsden
Copy link
Contributor

I could take a look at this if I know what the expected behavior should be.

Would it be correct to not print until some data has been generated for at least one column? Or is the behavior currently correct?

@stale
Copy link

stale bot commented Dec 11, 2020

This issue has been automatically marked as "stale" because it has not had any activity for a while. It will be closed in 90 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Status: Stale No recent activity for issue label Dec 11, 2020
@stale stale bot closed this as completed Mar 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Indicates a good issue for first-time contributors Status: Stale No recent activity for issue Type: Regression Indicates a functional regression
Projects
None yet
Development

No branches or pull requests

5 participants