This a report about real production experiment using both Linux
software RAID and a Mylex hardware RAID controler (real production
tend to be even harder than tests, even on a lower load, since
more special situations append).
My production server has:
2 x 8GB linux software RAID 1, Buslogic
all sophisticated devices
and rather use simpler ones where the sophisticated features being
performed in free (source code available) softwares, that I can read
in case of failure.
Hubert Tonneau
* DAC960 RAID Driver Version 2.2.4 of 23 August 1999 *
Copyright 1998-1999 by Leonard N
da7" "/dev/hda5 /dev/hda6 /dev/hda7 /dev/hda8" 5 64*2^10'
The third parameter (5) is the requested RAID level.
The fourth parameter (64*2^10=64K) is the requested chunk size.
Regards,
Hubert Tonneau
er.
You should also be awared that if anything wrong appends during the
conversion (any io error), the program will abort ungracefully and
all datas will be lost.
Good luck brave peoples
Hubert Tonneau
# Copyright (C) 1999 Hubert Tonneau [EMAIL PROTECTED]
#
# This program is free
What is the most reliable LVD SCSI controler for Linux ?
(I use several Buslogic controlers, but as far as I know they don't
have an LVD version, which is absolutely necessary for long SCSI chains,
and my Buslogic controlers went in an infinite reset loop several times,
which raid cannot
With the following configuration, any attempt to access /dev/md1 will
lock the process in D (disk sleep) state:
raiddev /dev/md0
raid-level1
nr-raid-disks 2
nr-spare-disks0
persistent-superblock 1
chunk-size64
Applying raid0145-19990724-2.0.37 will make kernel 2.0.37 modules fail
to compile if CONFIG_BLK_DEV_SR is selected as module.
(no problem with 2.2.12-pre4 for the same configuration)
gcc -D__KERNEL__ -I/usr/src/linux-2.0.37/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer
-a' complained something
like 'bad argument' or 'bad device' (sorry i don't remember the exact
message)
Lastly I switched to 2.2.12-pre4 kernel and everything ran just fine.
Regards,
Hubert Tonneau