From: "David Lethe" <david@santools.com>
To: David Rees <drees76@gmail.com>, michael@kmaclub.com
Cc: Richard Scobie <richard@sauce.co.nz>,
Mike McCarthy <mike@w1nr.net>, Bill Davidsen <davidsen@tmr.com>,
Michael Bussmann <bus@mb-net.net>,
linux-raid@vger.kernel.org
Subject: Re: Software RAID1 deadlock in 2.6.25 kernels
Date: Tue, 1 Jul 2008 15:21:00 -0500 [thread overview]
Message-ID: <108e01c8dbb8$0ae69674$e90df40a@exchange.rackspace.com> (raw)
Sounds like you worked for microsoft ... "i have 3 systems running XP and I never had a blue screen of death, so there is nothing wrong with the OS" :)
david
-----Original Message-----
From: "David Rees" <drees76@gmail.com>
Subj: Re: Software RAID1 deadlock in 2.6.25 kernels
Date: Tue Jul 1, 2008 2:03 pm
Size: 1K
To: "michael@kmaclub.com" <michael@kmaclub.com>
cc: "Richard Scobie" <richard@sauce.co.nz>; "Mike McCarthy" <mike@w1nr.net>; "Bill Davidsen" <davidsen@tmr.com>; "Michael Bussmann" <bus@mb-net.net>; "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
On Mon, Jun 30, 2008 at 1:19 PM, michael@kmaclub.com
<michael@kmaclub.com> wrote:
> Richard Scobie wrote:
>> 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)
>>
>> FC9 running on RAID 1 (ata_piix) for the last 3 weeks or so, with no
>> trouble.
>
> Same here. I haven't had any issues with RAID 1 on Fedora 9.
>
> So the issue isn't biting everyone but there is always the chance something
> is wrong with a specific controller or configuration.
FWIW, me too. I have three different Fedora 9 systems running the
latest Fedora kernels based on 2.6.25 which are running software RAID
1 without any issues at all.
-Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2008-07-01 20:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 20:21 David Lethe [this message]
2008-07-01 21:24 ` Software RAID1 deadlock in 2.6.25 kernels michael
2008-07-01 21:42 ` David Rees
[not found] <48650567.3000501@w1nr.net>
2008-06-27 20:47 ` 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
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='108e01c8dbb8$0ae69674$e90df40a@exchange.rackspace.com' \
--to=david@santools.com \
--cc=bus@mb-net.net \
--cc=davidsen@tmr.com \
--cc=drees76@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=michael@kmaclub.com \
--cc=mike@w1nr.net \
--cc=richard@sauce.co.nz \
/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).