Hello, I am setting up an app server and want to maximize SQL performance
as much as possible without hurting transfer of files 20-100k too much.
I am running mysql 3.22.20a on a raid5 array with three 4GB disks and a
chunk size of 128k
I am running sql-bench now, concentrating on select perform
Hi,
On Tue, 06 Apr 1999 10:39:21 +0100, Richard Jones
<[EMAIL PROTECTED]> said:
> Can it be a cabling fault? I thought that SCSI had parity
> checking.
Yes, it does, and all _decent_ scsi cards support it. Some old ones do
not (especially ISA cards).
--Stephen
I had a similar experience and got around it using:
ckraid --force-check --fix /dev/md0
I attributed to immature software that errs on the side of caution...
If I recall I had a similar situation with ext2 in the early days.
On Tue, 6 Apr 1999, Linux SMP Mlist wrote:
> Hi,
>
> i have /d
Download the vanilla kernel of 2.0.36 and patch from there.
On Tue, 6 Apr 1999, Michael Mansour wrote:
> Hi,
>
> I have attempted applying the raid-04etc patch (sorry, forgot the exact
> name) onto the kernel 2.0.36 (rh5.2) with:
>
> cat raid-04etc | patch -p0
>
> The patch stops at the buff
Hi,
i have /dev/sda3 a /dev/sdb3 in RAID1 array.
I've run raidadd /dev/md0, raidrun /dev/md0 - OK.
mount /dev/md0 - OK
raidstop /dev/md0 - OK
mount /dev/sda3 /mnt/ OK
umount /mnt OK
Now i've tried to start raid device but ...
raidadd /dev/md0 OK
raidrun /dev/md0 - > "raid1: detected m
"Stephen C. Tweedie" wrote:
>
> Hi,
>
> On Mon, 29 Mar 1999 11:28:25 +0100, Richard Jones
> <[EMAIL PROTECTED]> said:
>
> > Not so fast there :-)
>
> > Mar 26 20:52:35 fred kernel: EXT2-fs error (device md(9,0)): ext2_free_blocks:
>Freeing blocks not in datazone - block = 550046767, count = 1
Hi,
I have attempted applying the raid-04etc patch (sorry, forgot the exact
name) onto the kernel 2.0.36 (rh5.2) with:
cat raid-04etc | patch -p0
The patch stops at the buffer.c section.
Is there anything wrong with what I am doing or is there other issues to
this I don't know about.
Thankyou
On Sat Apr 03 04:09:57 1999, [EMAIL PROTECTED] wrote:
> i now give the kernel boot time args;
...
> then it works fine, fdisk see the same as everyone else.
I've had same with two identical SCSI drives. I just calculated which
one gave more space and changed other one to those settings (using
fdi
have you considered an upgrade to 2.2.x ? i would be interested to see if
problem persists. we are using newest raid code on several uni-proc boxes, no
problems, even with very heavy load. we only using old raid code on SMP boxes.
had considered upgrading to 2.2.x and new raid code on these.
all
