linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Mon, 07 Jul 2008 23:24:31 -0400	[thread overview]
Message-ID: <4872DDEF.8040109@tmr.com> (raw)
In-Reply-To: <48725C4B.5030505@w1nr.net>

Mike McCarthy wrote:
> Bill Davidsen wrote:
>> Mike McCarthy wrote:
>>> Bill Davidsen wrote:
>>>>
>>>> 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?
>>>>
>>> No.  This system and the drives pre-date NCQ.  I think NCQ is only 
>>> implemented in SATA and these are IDE drives.  Sometime over the 
>>> weekend, I am going to reload SUSE 11 and try to do some more 
>>> debugging.
>>>
>>> BTW: It's back to 10.3 (kernel 2.6.22) running happily with a VMware 
>>> server thrashing away at the disks.
>>
>> This has recycled back to the top of my todo list, I have a server in 
>> mothballs with IDE drives, I'll pull it out, upgrade to FC9 current 
>> (non-rawhide) and see if I have any problems. It's off due to lack of 
>> need, not really obsolete, so it's a fair test. O'll put a dew 
>> hundred GB of raid-1 and beat on it.
>>
> I was going to get back to you all today and let you know what I 
> found.  On Thursday, I rebuilt the system with SUSE 11 but before I 
> did I went over all of the BIOS settings.  The second IDE drive was 
> set to "NONE" instead of "AUTO".  Well, the installation went without 
> the previous hitch of having to manually install grub on the first 
> boot after the install.  It has also been running since then without 
> issue.
>
> Is it that simple?  Could that be all that was wrong?  What doesn't 
> make sense is how 10.3 (kernel 2.6.22) never had an issue.  Perhaps 
> without the BIOS reporting the second drive, the later kernel chose 
> the wrong parameters setting it up and they didn't match what was set 
> up by the BIOS for the first drive?

Oh well, I needed to upgrade that system, I'll push testing down the 
week a day or two. It could well have been that simple.

-- 
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 



  reply	other threads:[~2008-07-08  3:24 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
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 [this message]
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=4872DDEF.8040109@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).