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

fsmon vs fs_usage #28

Open
alvarofe opened this issue Sep 15, 2016 · 2 comments
Open

fsmon vs fs_usage #28

alvarofe opened this issue Sep 15, 2016 · 2 comments

Comments

@alvarofe
Copy link

It's true that the output from fsmon is nicer than fs_usage but it doesn't lose any event.


$ sudo fs_usage 43
18:28:12.852614  write             F=14   B=0x4f                                                                                        0.000005   syslogd.2809400
18:28:12.852748  write             F=14   B=0x78                                                                                        0.000009   syslogd.2808983
18:28:12.852838  write             F=14   B=0x59                                                                                        0.000009   syslogd.2808983
18:28:12.854518  write             F=14   B=0x63                                                                                        0.000011   syslogd.2809400
18:28:22.015680  lseek             F=7    O=0x00000000         <UNKNOWN>                                                                0.000002   syslogd.2809428
18:28:22.017050  write             F=7    B=0x8                                                                                         0.001370   syslogd.2809428
18:28:22.017079  lseek             F=12   O=0x000aecfc         <UNKNOWN>                                                                0.000003   syslogd.2809428
18:28:22.018387  write             F=12   B=0x9a                                                                                        0.001307   syslogd.2809428
18:28:22.018390  lseek             F=12   O=0x000aec68         <UNKNOWN>                                                                0.000001   syslogd.2809428
18:28:22.018393  write             F=12   B=0x8                                                                                         0.000003   syslogd.2809428
18:28:22.018394  lseek             F=12   O=0x00000025         <UNKNOWN>                                                                0.000001   syslogd.2809428
18:28:22.019752  write             F=12   B=0x8                                                                                         0.001359   syslogd.2809428
18:28:22.019756  lseek             F=12   O=0x000aed96         <UNKNOWN>                                                                0.000002   syslogd.2809428
18:28:22.021179  write             F=8    B=0x84

From fsmon I had to change different backends any of them were working except fsevapi but is giving the following output, quite hard to make head or tails from it.

captura de pantalla 2016-09-15 a las 18 29 17

The process that I am monitoring with the purpose to explore the tool is syslogd. I wouldn't mind to look at this issue and working on the output, but busy these days. Will try in the following weeks

@trufae
Copy link
Member

trufae commented Sep 15, 2016

fsusage uses the fsevapi afaik, thats because output is the same in both ;)

each filesystem backend supports different events.

the output i get from fsmon -b fsevapi is exactly like the one in others, so i cant reproduce this issue

On 15 Sep 2016, at 18:34, Álvaro Felipe Melchor [email protected] wrote:

It's true that the output from fsmon is nicer than fs_usage but it doesn't lose any event.

$ sudo fs_usage 43
18:28:12.852614 write F=14 B=0x4f 0.000005 syslogd.2809400
18:28:12.852748 write F=14 B=0x78 0.000009 syslogd.2808983
18:28:12.852838 write F=14 B=0x59 0.000009 syslogd.2808983
18:28:12.854518 write F=14 B=0x63 0.000011 syslogd.2809400
18:28:22.015680 lseek F=7 O=0x00000000 0.000002 syslogd.2809428
18:28:22.017050 write F=7 B=0x8 0.001370 syslogd.2809428
18:28:22.017079 lseek F=12 O=0x000aecfc 0.000003 syslogd.2809428
18:28:22.018387 write F=12 B=0x9a 0.001307 syslogd.2809428
18:28:22.018390 lseek F=12 O=0x000aec68 0.000001 syslogd.2809428
18:28:22.018393 write F=12 B=0x8 0.000003 syslogd.2809428
18:28:22.018394 lseek F=12 O=0x00000025 0.000001 syslogd.2809428
18:28:22.019752 write F=12 B=0x8 0.001359 syslogd.2809428
18:28:22.019756 lseek F=12 O=0x000aed96 0.000002 syslogd.2809428
18:28:22.021179 write F=8 B=0x84
From fsmon I had to change different backends any of them were working except fsevapi but is giving the following output, quite hard to make head or tails from it.

https://cloud.githubusercontent.com/assets/3474042/18558172/629aca12-7b72-11e6-8da1-bd1250d141a3.png
The process that I am monitoring with the purpose to explore the tool is syslogd. I wouldn't mind to look at this issue and working on the output, but busy these days. Will try in the following weeks


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub #28, or mute the thread https://github.com/notifications/unsubscribe-auth/AGIjG-8HqnifQsRO8GGD2Wt4WhrcAH8sks5qqXOLgaJpZM4J-E7x.

@trufae
Copy link
Member

trufae commented Dec 12, 2017

ping?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants