From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com,
Keir Fraser <keir.fraser@eu.citrix.com>,
Kouya Shimura <kouya@jp.fujitsu.com>,
Samuel Thibault <samuel.thibault@eu.citrix.com>
Subject: Re: Windows Bug Check 0x101 issue
Date: Wed, 26 Mar 2008 12:34:47 +0000 [thread overview]
Message-ID: <20080326123447.2397261d@core> (raw)
In-Reply-To: <18410.10932.522487.743717@mariner.uk.xensource.com>
> Hrm. I think it would be better to return an endless sequence of
> errors than to return no error at all. Since we don't know which
> block failed, we could report an error flushing block 0, and then an
> error flushing block 1, and so on ?
On a raid volume that will give wrong results and incorrect recovery
behaviour. You need to report correct information. In addition a lot of
software treats repeated errors on flush as a device failure after a
certain count.
If a write to the underlying emulated media fails you know at least which
write fails and usually the page that failed (as you get a short write)
Alan
next prev parent reply other threads:[~2008-03-26 12:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-24 9:53 Windows Bug Check 0x101 issue Kouya Shimura
2008-03-24 11:01 ` Samuel Thibault
2008-03-24 11:05 ` Keir Fraser
2008-03-25 10:54 ` Kouya Shimura
2008-03-25 10:59 ` Keir Fraser
2008-03-25 11:28 ` Ian Jackson
2008-03-25 17:57 ` Samuel Thibault
2008-03-26 7:07 ` Kouya Shimura
2008-03-26 10:13 ` Samuel Thibault
2008-03-26 10:29 ` Ian Jackson
2008-03-26 10:27 ` Alan Cox
2008-03-26 10:51 ` Ian Jackson
2008-03-26 12:34 ` Alan Cox [this message]
2008-03-26 14:18 ` Ian Jackson
2008-03-26 10:39 ` Ian Jackson
2008-03-27 5:20 ` Kouya Shimura
2008-03-27 9:08 ` Alan Cox
2008-03-27 16:34 ` Ian Jackson
2008-03-27 16:30 ` Alan Cox
2008-03-27 17:39 ` Ian Jackson
2008-03-28 3:09 ` Kouya Shimura
[not found] ` <87k5jnl7qt.fsf@basil.nowhere.org>
2008-03-28 9:32 ` Ian Jackson
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=20080326123447.2397261d@core \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Ian.Jackson@eu.citrix.com \
--cc=keir.fraser@eu.citrix.com \
--cc=kouya@jp.fujitsu.com \
--cc=samuel.thibault@eu.citrix.com \
--cc=xen-devel@lists.xensource.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 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.