From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] report read/write errors to IDE guest driver as ECC errorsj
Date: Mon, 11 Aug 2008 18:01:23 +0100 [thread overview]
Message-ID: <20080811170123.GU4499@implementation.uk.xensource.com> (raw)
In-Reply-To: <18592.27928.201904.615457@mariner.uk.xensource.com>
Ian Jackson, le Mon 11 Aug 2008 17:47:20 +0100, a écrit :
> > Special ENOSPC handling can be added on top.
> > I agree that pausing the guest is probably best option in that scenario,
>
> I disagree. Most reasonable guests will have special handling for
> write failures on their disks. For example, Linux will (in the
> default setup) remount the fs readonly precisely to prevent
> corruption.
Actually no, see the thread
"ext3 seems to ignore ECC errors"
http://marc.info/?l=linux-kernel&m=121786230719154&w=2
> Pausing the guest denies the guest the ability to take whatever action
> it really wants to.
Sure, but I'm afraid of e.g. guests that would handle it by thinking
"bad sector, let's mark it as such and try another one".
Samuel
next prev parent reply other threads:[~2008-08-11 17:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 11:55 [Qemu-devel] [PATCH] report read/write errors to IDE guest driver as ECC errors Samuel Thibault
2008-08-06 2:26 ` Anthony Liguori
2008-08-06 9:28 ` Daniel P. Berrange
2008-08-06 12:22 ` Jamie Lokier
2008-08-11 16:47 ` Ian Jackson
2008-08-11 17:01 ` Samuel Thibault [this message]
2008-08-11 17:56 ` [Qemu-devel] [PATCH] report read/write errors to IDE guest driver as ECC errorsj Jamie Lokier
2008-08-11 17:05 ` [Qemu-devel] [PATCH] report read/write errors to IDE guest driver as ECC errors Anthony Liguori
2008-08-06 16:21 ` [Qemu-devel] " Samuel Thibault
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=20080811170123.GU4499@implementation.uk.xensource.com \
--to=samuel.thibault@ens-lyon.org \
--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).