From: Andy Smith <andy@strugglers.net>
To: xen-devel@lists.xenproject.org
Subject: Re: dom0 suddenly blocking on all access to md device
Date: Tue, 2 Mar 2021 00:44:34 +0000 [thread overview]
Message-ID: <20210302004434.GG29212@bitfolk.com> (raw)
In-Reply-To: <20210226223927.GQ29212@bitfolk.com>
Hello,
On Fri, Feb 26, 2021 at 10:39:27PM +0000, Andy Smith wrote:
> just lately I've been sporadically having issues where dom0 blocks
> or severely slows down on all access to the particular md device
> that hosts all domU block devices.
This just happened again on the same server as the previous
occurrence on 26th February.
Again I was able to get things going again and avoid having to
destroy all guests and hard reset the host by doing a destroy on a
guest that was seen to be trying to do the most block IO (through
xentop).
This means that this particular host is still on Debian buster
kernel 4.19.0-13-amd64 and credit2 scheduler. As it's been only a
few days this might present itself again on this host quite soon. Is
there any useful information I can provide when it does?
Unfortunately there were no logs of interest neither in the dom0
syslog, guest syslog nor dom0 serial console. After the heavy IO
guest was destroyed dom0 syslog did give:
Mar 2 00:14:08 clockwork kernel: [6732447.973298] xen-blkback: Scheduled work from previous purge is still busy, cannot purge list
…but I assume that is just a result of IO springing back to life.
Thanks,
Andy
next prev parent reply other threads:[~2021-03-02 0:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 22:39 dom0 suddenly blocking on all access to md device Andy Smith
2021-02-26 22:50 ` Andy Smith
2021-03-02 0:44 ` Andy Smith [this message]
2021-06-12 14:11 ` Andy Smith
2021-06-12 22:47 ` Rob Townley
2021-06-12 23:13 ` Andy Smith
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=20210302004434.GG29212@bitfolk.com \
--to=andy@strugglers.net \
--cc=xen-devel@lists.xenproject.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 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).