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

Tools for tracking down I/O Wait #2039

Open
eMPee584 opened this issue Oct 17, 2023 · 3 comments
Open

Tools for tracking down I/O Wait #2039

eMPee584 opened this issue Oct 17, 2023 · 3 comments

Comments

@eMPee584
Copy link

Because in practice, systems often get stuck in high iowait scenarios, it would be great to have tools for diagnosing this in sysdig.
Example questions would be:

  • Which application has stuck IO in flight?
  • Which files and which storage blocks are being accessed?
  • Stalling due to networked filesystems connection failure / starving?
  • Swapping activity as special case
  • correlation with pressure stall information (PSI)
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Jun 15, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 23, 2024
@eMPee584
Copy link
Author

Well ok the issue is stale yes, but it is not quite resolved. At the moment, to track disk I/O traffic and the source application, one has to combine multiple tools like diskgraph, nmon, iotop, fatrace, blktrace et cetera..

@therealbobo therealbobo reopened this Jul 18, 2024
@github-actions github-actions bot removed the stale label Jul 19, 2024
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