From: Bill Davidsen <davidsen@tmr.com>
To: Mike McCarthy <mike@w1nr.net>
Cc: Michael Bussmann <bus@mb-net.net>, linux-raid@vger.kernel.org
Subject: Re: Software RAID1 deadlock in 2.6.25 kernels
Date: Tue, 01 Jul 2008 11:34:19 -0400 [thread overview]
Message-ID: <486A4E7B.50604@tmr.com> (raw)
In-Reply-To: <4868E45F.30105@w1nr.net>
Mike McCarthy wrote:
> Bill Davidsen wrote:
>>
>> Wonder if hardware or software is happening, sounds like an
>> mishandled hardware error, but I'm guessing. I have a server with
>> RAID1 and Fedora 2.6.22.14-72.fc6PAE kernel, up 72 days, no problems.
>>
>
> 2.6.22 is running fine. The problems are in the 2.6.25 kernel (FC9
> and SUSE 11.0)
Given heavy 2.6.25 use, my guess is still that the root cause of this is
hardware, and that the change in disk code either triggers the hardware
problem, or handles it differently. Are you by any chance running NCQ on
your system?
--
Bill Davidsen <davidsen@tmr.com>
"Woe unto the statesman who makes war without a reason that will still
be valid when the war is over..." Otto von Bismark
next prev parent reply other threads:[~2008-07-01 15:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48650567.3000501@w1nr.net>
2008-06-27 20:47 ` Software RAID1 deadlock in 2.6.25 kernels Neil Brown
2008-06-30 9:23 ` Gabor Gombas
2008-06-30 11:31 ` Mike McCarthy
2008-06-30 11:59 ` Michael Bussmann
2008-06-30 13:32 ` Bill Davidsen
2008-06-30 13:49 ` Mike McCarthy
2008-06-30 13:56 ` Justin Piszcz
2008-06-30 20:21 ` Richard Scobie
2008-06-30 20:19 ` michael
2008-07-01 19:00 ` David Rees
2008-07-01 15:34 ` Bill Davidsen [this message]
2008-07-01 17:00 ` Mike McCarthy
2008-07-01 19:45 ` Michael Bussmann
2008-07-02 10:37 ` Gabor Gombas
2008-07-02 10:50 ` Gabor Gombas
2008-07-07 16:07 ` Bill Davidsen
2008-07-07 18:11 ` Mike McCarthy
2008-07-08 3:24 ` Bill Davidsen
2008-07-01 20:21 David Lethe
2008-07-01 21:24 ` michael
2008-07-01 21:42 ` David Rees
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=486A4E7B.50604@tmr.com \
--to=davidsen@tmr.com \
--cc=bus@mb-net.net \
--cc=linux-raid@vger.kernel.org \
--cc=mike@w1nr.net \
/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).