From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LccX7-0007mr-Nj for qemu-devel@nongnu.org; Thu, 26 Feb 2009 04:27:57 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LccX6-0007lt-4P for qemu-devel@nongnu.org; Thu, 26 Feb 2009 04:27:57 -0500 Received: from [199.232.76.173] (port=34899 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LccX5-0007lq-VC for qemu-devel@nongnu.org; Thu, 26 Feb 2009 04:27:56 -0500 Received: from mx2.redhat.com ([66.187.237.31]:59827) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LccX4-0007D4-0D for qemu-devel@nongnu.org; Thu, 26 Feb 2009 04:27:55 -0500 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id n1Q9Rpji026950 for ; Thu, 26 Feb 2009 04:27:51 -0500 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n1Q9Rpsc003162 for ; Thu, 26 Feb 2009 04:27:52 -0500 Received: from dhcp-1-237.tlv.redhat.com (dhcp-1-237.tlv.redhat.com [10.35.1.237]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id n1Q9RoJU016805 for ; Thu, 26 Feb 2009 04:27:51 -0500 Date: Thu, 26 Feb 2009 11:24:43 +0200 From: Gleb Natapov Subject: Re: [Qemu-devel] [6388] Stop VM on ENOSPC error. Message-ID: <20090226092443.GF8810@redhat.com> References: <49A577FD.60701@codemonkey.ws> <20090225170422.GD8810@redhat.com> <49A57EF4.9030806@redhat.com> <20090225173822.GB14631@shareable.org> <49A65EF4.2030404@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49A65EF4.2030404@redhat.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org 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.