qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [6388] Stop VM on ENOSPC error.
Date: Wed, 25 Feb 2009 17:34:29 +0000	[thread overview]
Message-ID: <20090225173429.GV24969@redhat.com> (raw)
In-Reply-To: <20090225170422.GD8810@redhat.com>

On Wed, Feb 25, 2009 at 07:04:22PM +0200, Gleb Natapov wrote:
> On Wed, Feb 25, 2009 at 10:55:25AM -0600, Anthony Liguori wrote:
> > Anthony Liguori wrote:
> >> Revision: 6388
> >>           http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=6388
> >> Author:   aliguori
> >> Date:     2009-01-21 18:59:04 +0000 (Wed, 21 Jan 2009)
> >>
> >> Log Message:
> >> -----------
> >> Stop VM on ENOSPC error. (Gleb Natapov)
> >>
> >> This version of the patch adds new option "werror" to -drive flag.
> >> Possible values are:
> >>
> >> report    - report errors to a guest as IO errors
> >> ignore    - continue as if nothing happened
> >> stop      - stop VM on any error and retry last command on resume
> >> enospc    - stop vm on ENOSPC error and retry last command on resume
> >>             all other errors are reported to a guest.
> >>
> >> Default is "report" to maintain current behaviour.
> >>   
> >
> > I recently got burnt by the default being "report".  I was doing an  
> > installation and ran out of disk space.  The guest did not do anything  
> > intelligible with the error reports and froze very hard (as you'd 
> > expect).
> >
> > Any objection to changing to default to enospc?
> >
> Or even to stop. What guest can do with other errors anyway?

The idea is that if the guest at least sees the I/O error, then it won't
continue writing as if everything were OK. It may not be able to continue
normal operation, but it can at least mark the FS read-only and avoid
ongoing damage. So you have a reasonable liklihood of shutting down the
guest, fixing the ENOSPC problem ont he host, and starting the guests
again & them recovering their journal.  'ignore' is guarenteed dataloss,
'report' gives you a good fighting chance. 'stop'/'enospc' are best, if
the management app is able to detect that the VM is being paused & thus
report it to the user

Daniel
-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

  parent reply	other threads:[~2009-02-25 17:34 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
2009-02-25 17:34     ` Daniel P. Berrange [this message]
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=20090225173429.GV24969@redhat.com \
    --to=berrange@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 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).