qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	hch@infradead.org, qemu-devel@nongnu.org,
	Jes.Sorensen@redhat.com, stefanha@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] Re: [PATCH] For AIO return -ENOSPC on short write
Date: Tue, 1 Mar 2011 21:19:26 +0100	[thread overview]
Message-ID: <20110301201926.GA11734@lst.de> (raw)
In-Reply-To: <4D63EB55.2000800@redhat.com>

On Tue, Feb 22, 2011 at 05:59:01PM +0100, Paolo Bonzini wrote:
> On 02/22/2011 04:16 PM, Stefan Hajnoczi wrote:
> >Yes it is.  It doesn't explain it though.  The code involved here is
> >linux-aio.c and will be qcow2's bs->file.  That ought to be a
> >host_device and AFAIK that is not growable.  So I wanted to figure out
> >why we're even getting this far.  I expected the request to get
> >rejected in block.c when checking the range against the host_device.
> 
> Possibly a COW logical volume can give short writes on disk full?

It shouldn't.  If it does that needs fixing.

      reply	other threads:[~2011-03-01 20:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-22 10:17 [Qemu-devel] [PATCH] For AIO return -ENOSPC on short write Jes.Sorensen
2011-02-22 10:18 ` Jes.Sorensen
2011-02-22 11:44   ` [Qemu-devel] " Kevin Wolf
2011-02-22 11:45     ` Jes Sorensen
2011-02-22 13:56       ` Avi Kivity
2011-02-22 15:02   ` [Qemu-devel] " Stefan Hajnoczi
2011-02-22 15:11     ` Kevin Wolf
2011-02-22 15:16       ` Stefan Hajnoczi
2011-02-22 16:59         ` [Qemu-devel] " Paolo Bonzini
2011-03-01 20:19           ` Christoph Hellwig [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=20110301201926.GA11734@lst.de \
    --to=hch@lst.de \
    --cc=Jes.Sorensen@redhat.com \
    --cc=hch@infradead.org \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@linux.vnet.ibm.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).