From: Ville Herva <vherva@niksula.hut.fi>
To: Willy Tarreau <willy@w.ods.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ide write cache issue? [Re: Something corrupts raid5 disks slightly during reboot]
Date: Sat, 1 Nov 2003 23:02:23 +0200 [thread overview]
Message-ID: <20031101210223.GM4640@niksula.cs.hut.fi> (raw)
In-Reply-To: <20031101190114.GA936@alpha.home.local>
On Sat, Nov 01, 2003 at 08:01:14PM +0100, you [Willy Tarreau] wrote:
> On Sat, Nov 01, 2003 at 08:25:18PM +0200, Ville Herva wrote:
>
> > Is there anything special in booting to DOS instead of different linux
> > kernel, other than that it would rule out some strange kernel bug that is
> > present in 2.2 and 2.4?
>
> No, it was just to quicky confirm or deny the fact that it's the kernel
> which causes the problem. It could have been a long standing bug in the IDE
> or partition code, and which is present in several kernels.
I vaguely recall some ide write cache flushing code was fixed some time ago,
but I can't find it in the archives. Maybe I dreamed that up. But I still
wonder why an otherwise idle drive would hold the data in write cache for so
long (several minutes.)
> But as you say that it affects two different controllers, there's little
> chance that it's caused by anything except linux itself.
Unless the drive is buggy wrt. flushing its write cache. But I think it's
a quite distant possibility.
> Then, the reboot on DOS will only tell you if the drives were corrupted at
> startup or at shutdown.
Yep. I'll try to find the moment to boot the beast into something else than
the current kernel / distro (it could in theory be something in userspace,
though I cannot think what).
> > BTW: the corruption happens on warm reboots (running reboot command), not
> > just on power off / on.
>
> OK, but the BIOS scans your disks even during warm reboots.
True, I mainly made this note because I hadn't mentioned it before in the
thread, and I thought it might have some relevance wrt. possible ide write
caching problems. I didn't mean it as a response to the BIOS theory.
-- v --
v@iki.fi
next prev parent reply other threads:[~2003-11-01 21:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-31 19:08 Something corrupts raid5 disks slightly during reboot Ville Herva
2003-11-01 1:41 ` Jeffrey E. Hundstad
2003-11-01 1:57 ` Mike Fedyk
2003-11-01 8:33 ` Ville Herva
2003-11-01 8:27 ` ide write cache issue? [Re: Something corrupts raid5 disks slightly during reboot] Ville Herva
2003-11-01 15:56 ` Willy Tarreau
2003-11-01 18:25 ` Ville Herva
2003-11-01 19:01 ` Willy Tarreau
2003-11-01 21:02 ` Ville Herva [this message]
2003-11-02 6:05 ` Andre Hedrick
2003-11-02 8:28 ` Ville Herva
2003-11-02 20:57 ` Matthias Andree
2003-11-03 5:34 ` Andre Hedrick
2003-11-03 6:38 ` Ville Herva
2004-01-02 19:42 ` Something corrupts raid5 disks slightly during reboot Ville Herva
2004-01-02 20:02 ` Ville Herva
2004-01-14 14:46 ` Ville Herva
2004-01-14 22:22 ` Willy Tarreau
2004-01-14 22:46 ` Ville Herva
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=20031101210223.GM4640@niksula.cs.hut.fi \
--to=vherva@niksula.hut.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@w.ods.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).