From: Johannes Truschnigg <johannes@truschnigg.info>
To: eyal@eyal.emu.id.au
Cc: linux-raid@vger.kernel.org
Subject: Re: extremely slow writes to array [now not degraded]
Date: Mon, 13 Nov 2023 07:54:52 +0100 [thread overview]
Message-ID: <ZVHIPNwC2RKTVmok@vault.lan> (raw)
In-Reply-To: <1d0fb40a-1908-4b5e-9856-a5b79eafdc9c@eyal.emu.id.au>
[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]
You will need to generate some kind of call stack/graph info to start making
sense of the mess your running kernel gets itself into in the scenario you
described.
I imagine that looking at `perf` (`perf top` in particular; it should suffice
to paste a few instances of its topmost lines when the involved kernel threads
are spinning) would yield some useful data to kick off a potentially
productive debate about what could actually be going on.
On Fedora, I think `sudo dnf install perf` should set up everything you need
to get you going; then, look at `sudo perf top -F 999` for a while, and let
the list know what you see. (You can use your terminal emulator's flow control
features, available via Ctrl+S to enable and Ctrl+Q to disable, to "freeze"
the output to make it easier to copy it into a clipboard buffer.)
--
with best regards:
- Johannes Truschnigg ( johannes@truschnigg.info )
www: https://johannes.truschnigg.info/
phone: +436502133337
xmpp: johannes@truschnigg.info
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-11-13 6:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-05 23:06 extremely slow writes to degraded array eyal
2023-11-07 21:14 ` Peter Grandi
2023-11-08 1:37 ` eyal
2023-11-08 5:32 ` eyal
2023-11-08 16:50 ` Peter Grandi
2023-11-09 2:59 ` extremely slow writes to array [now not degraded] eyal
2023-11-09 13:16 ` Roger Heflin
2023-11-13 0:53 ` eyal
2023-11-13 6:54 ` Johannes Truschnigg [this message]
2023-11-13 8:06 ` eyal
2023-11-13 9:20 ` Johannes Truschnigg
2023-11-13 9:36 ` eyal
2023-11-13 9:58 ` eyal
2023-11-13 10:09 ` Johannes Truschnigg
2023-11-13 10:31 ` eyal
2023-11-13 12:26 ` Roger Heflin
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=ZVHIPNwC2RKTVmok@vault.lan \
--to=johannes@truschnigg.info \
--cc=eyal@eyal.emu.id.au \
--cc=linux-raid@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.