From: Johannes Truschnigg <johannes@truschnigg.info>
To: Dave Chinner <david@fromorbit.com>
Cc: Paul Menzel <pmenzel@molgen.mpg.de>,
linux-raid@vger.kernel.org, linux-nfs@vger.kernel.org,
linux-block@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: How to debug intermittent increasing md/inflight but no disk activity?
Date: Thu, 11 Jul 2024 10:51:39 +0200 [thread overview]
Message-ID: <Zo-dG8EGbfp_ghOB@vault.lan> (raw)
In-Reply-To: <Zo8VXAy5jTavSIO8@dread.disaster.area>
[-- Attachment #1: Type: text/plain, Size: 993 bytes --]
I just wanted to chime in to express a sincere "thank you!" to all of you
involved in this thread, for providing such a terrific example of how to
clearly and exhaustively present a systems problem, and then also how to
methodically determine its root cause.
If there were a textbook on this subject in the IT/CompSci context (if there
is, please let me know!), *this* exchange should make it into the next edition
on how to get problems analyzed and resolved.
I will keep it in my personal bookmarks right next to [0], which is a short
but great essay about how what you just put into practice is possible in
theory, and which I've used whenever needed to inspire hope in others (and,
truth be told, also in myself :)) in the face of the daunting complexity of
modern computer systems.
[0]: https://blog.nelhage.com/post/computers-can-be-understood/
--
with best regards:
- Johannes Truschnigg ( johannes@truschnigg.info )
www: https://johannes.truschnigg.info/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-07-11 9:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 11:46 How to debug intermittent increasing md/inflight but no disk activity? Paul Menzel
2024-07-10 11:54 ` Roger Heflin
2024-07-23 10:33 ` Paul Menzel
2024-07-10 23:12 ` Dave Chinner
2024-07-11 8:51 ` Johannes Truschnigg [this message]
2024-07-11 11:23 ` Andre Noll
2024-07-11 22:26 ` Dave Chinner
2024-07-13 15:47 ` Andre Noll
2024-07-23 15:13 ` Paul Menzel
2024-07-12 3:54 ` Dragan Milivojević
2024-07-12 23:45 ` Dave Chinner
2024-07-13 17:44 ` Dragan Milivojević
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Zo-dG8EGbfp_ghOB@vault.lan \
--to=johannes@truschnigg.info \
--cc=david@fromorbit.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).