From: Stefan Hajnoczi <stefanha@gmail.com>
To: linux-ext4@vger.kernel.org
Cc: kvm@vger.kernel.org, "Brian J. Murrell" <brian@interlinx.bc.ca>
Subject: Re: VMs are pausing with ENOSPC
Date: Mon, 11 Nov 2013 10:43:29 +0100 [thread overview]
Message-ID: <20131111094329.GF28264@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1383912032.27016.4.camel@pc.interlinx.bc.ca>
On Fri, Nov 08, 2013 at 07:00:32AM -0500, Brian J. Murrell wrote:
> On RHEL 6.4 I have a number of kvms using qemu raw disks. They are all
> on a filesystem which has reached 500G (of 1TB) of usage. None of the
> qemu images are full as reported by qemu-img info. Yet my VMs are all
> pausing with:
>
> block I/O error in device 'drive-virtio-disk0': No space left on device (28)
>
> in their logs
> i.e.: # qemu-img info /var/lib/libvirt/images/mgmt1-disk0
> image: /var/lib/libvirt/images/mgmt1-disk0
> file format: raw
> virtual size: 120G (128849018880 bytes)
> disk size: 52G
>
> and:
>
> # df -h /var/lib/libvirt/images/
> Filesystem Size Used Avail Use% Mounted on
> /dev/mapper/vg_00-virt--images 1.0T 500G 473G 52% /var/lib/libvirt/images
Added linux-ext4 mailing list and more info from an IRC debugging
session with Brian:
The image file is on an ext4 file system. The QEMU userspace process is
performing a pwritev() system call that fails with ENOSPC.
The particular pwritev() that failed had ~600 iovecs covering about 2.4
MB of data. The file is opened O_DIRECT.
The VMs are all hitting ENOSPC when they write to the file system but
df(1) shows there should still be 48% (~473 GB) available.
Any ideas why writes produce ENOSPC on an ext4 file system with
sufficient space free?
Stefan
next parent reply other threads:[~2013-11-11 9:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1383912032.27016.4.camel@pc.interlinx.bc.ca>
2013-11-11 9:43 ` Stefan Hajnoczi [this message]
2013-11-11 12:17 ` VMs are pausing with ENOSPC Lukáš Czerner
2013-11-11 12:22 ` Jan Kara
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=20131111094329.GF28264@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=brian@interlinx.bc.ca \
--cc=kvm@vger.kernel.org \
--cc=linux-ext4@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).