From: Roman Mamedov <rm@romanrm.net>
To: bo.li.liu@oracle.com
Cc: 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 10:08:52 +0500 [thread overview]
Message-ID: <20160120100852.470479a6@natsu> (raw)
In-Reply-To: <20160120001944.GA9884@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]
On Tue, 19 Jan 2016 16:19:44 -0800
Liu Bo <bo.li.liu@oracle.com> wrote:
> What about 'btrfs fi df' 's output on the directory where $NAME.img is
> located?
$ sudo btrfs fi df .
Data, single: total=8.59TiB, used=8.47TiB
System, DUP: total=32.00MiB, used=624.00KiB
Metadata, DUP: total=13.00GiB, used=9.87GiB
GlobalReserve, single: total=512.00MiB, used=0.00B
$ df -h .
Filesystem Size Used Avail Use% Mounted on
- 9.1T 8.5T 571G 94% /mnt/r5/vm
The guest VM disk itself is 8 GB in size.
> According to my experience, kvm guest can be 'no response' when no space
> on the backend's filesystem, but you said that the alternative way
> work, so it doesn't look like a no space issue.
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.
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-01-20 5: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 [this message]
2016-01-20 11:34 ` Paolo Bonzini
2016-01-20 15:08 ` Roman Mamedov
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=20160120100852.470479a6@natsu \
--to=rm@romanrm.net \
--cc=bo.li.liu@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=linux-btrfs@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 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).