lkml.org 
[lkml]   [2001]   [Sep]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: AIC + RAID1 error? (was: Re: aic7xxx errors)
Olaf Zaplinski schrieb:
>
> Okay, I tested it today, compiled 2.4.9ac10 with the new driver and TCQ set
> to 32. I built the driver as a module to make sure that the machine at least
> boots into runlevel 3 (I have no console access, only access to the reset
> switch).
>
> I rebooted and inserted the driver with 'modprobe aic7xxx', remembered that
> I forgot the verbose flag, removed the driver with 'modprobe -r' and
> re-inserted it with 'modprobe aic7xxx aic7xxx=verbose'. The machine was
> still alive then. But right after entering 'raidhotadd /dev/md1 /dev/sda1'
> the machine hung. reiserfs erased the last lines of /var/log/messages, but
> AFAIK the verbose driver output showed no errors.
>
> But how can I help to reproduce the error? Of course I could break the
> mirror, compile the driver into the kernel (non-module) and do some stress
> test on the SCSI drive. But it's not so good when I drive this machine into
> a hang too often.
>
> I compiled the old driver now, also with TCQ set to 32, and the machine
> seems to work fine.
>

Hello...

I`m also in the moment testing with my raid-problem where one drive
falls out of the raid...till now it did not happen with the old driver,
but that means nothing as it only happened once a week or so.

Something other made me wonder:
I ran the machine several times with the *new* aic7xxx-driver (TCQ=32)
and the "aic7xxx=verbose" commandline, and i noticed the following:
At every reboot (made by "reboot", RH7.1), the machine was not able to
stop the raid5 correctly...it un-mounted the mountpoint (/home) and then
it normaly wants to stop the raid...(you see the messages "mdrecoveryd
got waken up...") but that did not work and after some time (30sec) the
kernel Ooopsed. This was reproducable and only occured if booted with
the "aic7xxx=verbose" kernel-parameter.
The effect after reboot was, that the raid had to be resynced because
one partition (that which always falls out) was damaged or at least
seemed to.
(The filesystem was clean, that was already unmounted as the oops
occured.)

Perhaps someone can test if this is reproducable with his machine
too...i use kernel 2.4.3, raid is built-in, also the aic7xxx, there are
three raid-disks (LVD, aic7xxx-controller on Mobo) in a raid5 mounted as
/home.

Solong...
Frank.

--
Frank Schneider, <SPATZ1@T-ONLINE.DE>.
Microsoft isn't the answer.
Microsoft is the question, and the answer is NO.
... -.-
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:17    [W:0.099 / U:3.432 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site