From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@kernel.org
Subject: [Bug 200981] hypervisor fs hangs at heavy write activity on VM (kvm, qcow2 image) having a reflink disk copy
Date: Thu, 06 Sep 2018 05:36:37 +0000 [thread overview]
Message-ID: <bug-200981-201763-4R9Oo6UPfh@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-200981-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=200981
--- Comment #5 from Alexander Y. Fomichev (git.user@gmail.com) ---
Created attachment 278345
--> https://bugzilla.kernel.org/attachment.cgi?id=278345&action=edit
dmesg showing all locks held in the system
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2018-09-06 10:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 14:32 [Bug 200981] New: hypervisor fs hangs at heavy write activity on VM (kvm, qcow2 image) having a reflink disk copy bugzilla-daemon
2018-08-30 14:34 ` [Bug 200981] " bugzilla-daemon
2018-08-31 1:26 ` bugzilla-daemon
2018-08-31 7:39 ` bugzilla-daemon
2018-09-01 5:01 ` bugzilla-daemon
2018-09-06 5:36 ` bugzilla-daemon [this message]
2018-09-06 5:37 ` bugzilla-daemon
2018-09-06 5:39 ` bugzilla-daemon
2018-09-06 14:25 ` bugzilla-daemon
2018-09-06 16:52 ` bugzilla-daemon
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=bug-200981-201763-4R9Oo6UPfh@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-xfs@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 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).