From: Roman Mamedov <rm@romanrm.net>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: bo.li.liu@oracle.com, linux-btrfs@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: Kernel 4.4.0 KVM guest on Btrfs locks up on snapshotting
Date: Wed, 20 Jan 2016 20:08:00 +0500 [thread overview]
Message-ID: <20160120200800.6858d6ee@natsu> (raw)
In-Reply-To: <569F70AA.2030006@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1399 bytes --]
On Wed, 20 Jan 2016 12:34:02 +0100
Paolo Bonzini <pbonzini@redhat.com> wrote:
> On 20/01/2016 06:08, Roman Mamedov wrote:
> > I don't get any ENOSPC errors on the host, also it doesn't seem to
> > be a slowdown caused by disk I/O searching for free space, just a
> > complete lock-up: I monitor the guest with 'ping', and when it
> > happens, the ping responses stop immediately and do not return,
> > also there is no reaction to any keypress in the KVM VNC window.
>
> Can you go to the QEMU monitor (Ctrl-Alt-F2 typically, or just add
> "-monitor stdio" to the QEMU command line) and type "info status"?
Aha, now this is getting somewhere.
------------------
(qemu) info status
VM status: paused (io-error)
(qemu) info block
hd: vm.img (raw)
I/O status: nospace
Detect zeroes: unmap
ide1-cd0: [not inserted]
Removable device: not locked, tray closed
floppy0: [not inserted]
Removable device: not locked, tray closed
sd0: [not inserted]
Removable device: not locked, tray closed
(qemu) info block-jobs
No active jobs
------------------
So this seems to be an transient ENOSPC error returned to the data writing
process by the FS during snapshotting. I can now reproduce this without KVM,
just with dd. Seems not much to do with KVM then, I will post more details to
the btrfs list. Thanks!
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2016-01-20 15:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 22:02 Kernel 4.4.0 KVM guest on Btrfs locks up on snapshotting Roman Mamedov
2016-01-19 22:18 ` Paolo Bonzini
2016-01-19 23:03 ` Roman Mamedov
2016-01-20 8:28 ` Paolo Bonzini
2016-01-20 13:58 ` Roman Mamedov
2016-01-20 17:28 ` Paolo Bonzini
2016-01-20 18:46 ` Roman Mamedov
2016-01-20 20:38 ` Paolo Bonzini
2016-01-20 0:19 ` Liu Bo
2016-01-20 5:08 ` Roman Mamedov
2016-01-20 11:34 ` Paolo Bonzini
2016-01-20 15:08 ` Roman Mamedov [this message]
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=20160120200800.6858d6ee@natsu \
--to=rm@romanrm.net \
--cc=bo.li.liu@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=pbonzini@redhat.com \
/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).