From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Mike Dresser <mdresser_l@windsormachine.com>
Cc: Carsten Otto <carsten.otto@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Daily crashes, incorrect RAID behaviour
Date: Tue, 15 Aug 2006 20:27:09 +0100 [thread overview]
Message-ID: <200608152027.09880.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.0608151423200.25217@router.windsormachine.com>
On Tuesday 15 August 2006 19:28, Mike Dresser wrote:
> On Tue, 15 Aug 2006, Carsten Otto wrote:
> > Okay, after Ralf's message I found this newsgroup post:
> > http://groups.google.de/group/linux.debian.user/msg/f12dec920523a629?hl=d
> >e&
> >
> >> You should be aware that currently
> >> Maxtor Maxline III's(7v300F0's) do not work properly due to a firmware
> >> bug. The current version shipping is VA111630, an update is available
> >> to VA111670 which merely reduces the frequency of timeouts that get the
> >> drive kicked out from the array.
>
> I'm running 680 now, and the 15 drives have been up for something like two
> months or so without issues at all.. Seems like the firmware fixes the
> problem.
Still, the RAID rebuild problem is worrying. I might have to deliberately
fault my RAID5 partitions and see if they rebuild correctly..
--
Cheers,
Alistair.
Final year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
prev parent reply other threads:[~2006-08-15 19:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-15 11:36 Carsten Otto
2006-08-15 12:33 ` Michael Tokarev
2006-08-15 12:57 ` Alan Cox
2006-08-15 12:42 ` Carsten Otto
2006-08-15 13:08 ` Jan Engelhardt
2006-08-15 13:45 ` Ralf Müller
2006-08-19 11:37 ` Andrew Baker
2006-08-19 11:47 ` Justin Piszcz
2006-08-19 18:53 ` Andrew Baker
2006-08-15 15:31 ` Carsten Otto
2006-08-15 18:28 ` Mike Dresser
2006-08-15 19:27 ` Alistair John Strachan [this message]
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=200608152027.09880.s0348365@sms.ed.ac.uk \
--to=s0348365@sms.ed.ac.uk \
--cc=carsten.otto@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mdresser_l@windsormachine.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®