From: Gleb Natapov <gleb@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [6388] Stop VM on ENOSPC error.
Date: Thu, 26 Feb 2009 11:24:43 +0200 [thread overview]
Message-ID: <20090226092443.GF8810@redhat.com> (raw)
In-Reply-To: <49A65EF4.2030404@redhat.com>
On Thu, Feb 26, 2009 at 11:20:52AM +0200, Avi Kivity wrote:
> Jamie Lokier wrote:
>> Avi Kivity wrote:
>>
>>> Gleb Natapov wrote:
>>>
>>>>> Any objection to changing to default to enospc?
>>>>>
>>>>>
>>>> Or even to stop. What guest can do with other errors anyway?
>>>>
>>> Softtware RAID-5 in the guest should be able to recover by reading
>>> from another stripe.
>>>
>>
>> These are read errors, not write errors.
>>
>
> I thought 'stop' considered all errors.
>
>
No, only write errors. That is why parameter is called werror. I thought
that handle write errors and read errors differently may be useful.
--
Gleb.
next prev parent reply other threads:[~2009-02-26 9:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 18:59 [Qemu-devel] [6388] Stop VM on ENOSPC error Anthony Liguori
2009-02-25 16:55 ` Anthony Liguori
2009-02-25 17:04 ` Gleb Natapov
2009-02-25 17:25 ` Avi Kivity
2009-02-25 17:38 ` Jamie Lokier
2009-02-26 9:20 ` Avi Kivity
2009-02-26 9:24 ` Gleb Natapov [this message]
2009-02-25 17:34 ` Daniel P. Berrange
2009-02-25 18:31 ` Anthony Liguori
2009-02-25 18:48 ` Jamie Lokier
2009-02-25 19:29 ` Anthony Liguori
2009-02-25 18:36 ` Jamie Lokier
2009-02-25 17:11 ` Avi Kivity
2009-02-25 18:26 ` Anthony Liguori
2009-02-26 9:17 ` Avi Kivity
2009-02-25 17:20 ` Daniel P. Berrange
2009-02-25 18:08 ` [Qemu-devel] " Jan Kiszka
2009-02-25 18:27 ` [Qemu-devel] " Anthony Liguori
2009-02-25 18:51 ` Jamie Lokier
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=20090226092443.GF8810@redhat.com \
--to=gleb@redhat.com \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.