At 09:28 PM 21/04/00 +0200, bert hubert wrote:
>- Forwarded message from Greg Baker <[EMAIL PROTECTED]> -
>
>Date: Fri, 21 Apr 2000 10:51:00 -0500 (CDT)
>From: Greg Baker <[EMAIL PROTECTED]>
>Subject: Re: VM: killing...
>To: unlisted-recipients: ;(no To-header on input)
>Cc: [EMAIL PROTECT
Vince,
I'm pretty sure you have some bad memory modules in you machine.
Make a mem test e.g. memtest86
to be sure that your memory is ok.
Georg
<[EMAIL PROTECTED]>
I'm actaully getting bit by the VM killing (insert a random app here) bug.
I only have the problem when I use 2.2.14smp + (linux mem=256) + software raid
Very strange. I'm waiting for the kernel gods to eventually fix/discover
the problem.
My .02
My prevoius post to linux-kernel:
Hello,
I h
- Forwarded message from Greg Baker <[EMAIL PROTECTED]> -
Date: Fri, 21 Apr 2000 10:51:00 -0500 (CDT)
From: Greg Baker <[EMAIL PROTECTED]>
Subject: Re: VM: killing...
To: unlisted-recipients: ;(no To-header on input)
Cc: [EMAIL PROTECTED]
I'm getting this problem on a stock RedHat 6.2 (
When my system boots I get these lines relating to md0
md0: max total readahead window set to 128k
md0: 1 data-disks, max readahead per data-disk: 128k
catting /proc/mdstat
gives me:
read_ahead 1024 sectors
should these numbers be the same.
Vince showing his ignorance.
--
Vincent Stoessel -
[Bill BAO]
> is there anybody doing the parity generation by using the
> drive XOR cmd (XDWRITE, XDREAD, XDPWRITE) ?
>
> we will start this kind of work in Linux raid,
> want to know anybody else is also doing the same thing.
> we're looking for cooperation.
When I last reviewed FC-AL, I have
"Leonard N. Zubkoff" wrote:
>
> From: "List User" <[EMAIL PROTECTED]>
> Date: Wed, 19 Apr 2000 20:03:01 -0500
>
> I was wondering if anyone here knew the status on the drivers for the
> Mylex ExtremeRaid 2000 card. Are they in beta yet?
>
> In the next 1-2 months I'm going t
