Oh yes, it's really only to play with... I only trust data to alpha
software once I've figured out how to break it.. GRINS!
Well, the problem is that I have simulated a failure of half of the
mirror, then put the disk back in (hot) and done "raidhotadd" the device
was added again but with a
James,
First of all, you probably want to reboot. This will rename your devices
to their typical values. To add a device into a failed raid slot, you
can use the raidhotadd command. do something like:
raidhotadd /dev/md0 /dev/hdc2
This will add the device to the raid set and start a res
Hi,
After testing various failure conditions, I seem to be stuck because the
system allocated new disk numbers to the disks
RAID1 conf printout:
--- wd:1 rd:2 nd:3
disk 0, s:0, o:1, n:0 rd:0 us:1 dev:hdb1
disk 1, s:0, o:0, n:1 rd:1 us:1 dev:[dev 00:00]
disk 2, s:1, o:0, n:2 rd:2 us:1 d
On 29-Jan-99 Hisaaki Shibata wrote:
> I tested raid performance with my linux box.
>
> Env. is ...
> o Intel "Providence" PR440FX motherboard
> o Dual Pentium Pro Processor (233 MHz)
> o 256 MB of RAM
^
>MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU
>
On Fri, Jan 29, 1999 at 10:54:37AM -0700, D. Lance Robinson thusly shaped the
electrons:
> I have also noticed this type of problem. It seems as though the RAID5
> driver generates a growing write backlog and keeps allocating new
> buffers when new asynchronous write requests get in. Eventually
Hello Mingo, I have applied the 2.2.0 patch to 2.2.1 & have one
.rej (mm/mmap.c.rej) not sure what to do with this one .
The necessary change here is not obvious to me .
The below '-' line in 2.2.1 now reads .
unsigned long last = (end + PGDIR_SIZE -1) &
Hi! raiders and thanks a lot for software RAID tools.
I tested raid performance with my linux box.
Env. is ...
o Intel "Providence" PR440FX motherboard
o Dual Pentium Pro Processor (233 MHz)
o 256 MB of RAM
o On board aic7880 SCSI controller
o Add on AHA-2940(Ver. 1.16)
o HP 2GB SCSI2 HDD x 5
On Fri, 29 Jan 1999, Mr. James W. Laferriere wrote:
> Or mount the floppy drive internal to the case
That, by the way, is also a good way to greatly reduce the dust inhalation
factor of a floppy drive...
-Andy
Global Auctions
http://www.globalauctions.com
On Fri, 29 Jan 1999, Thomas Pawlikaniec wrote:
> On Fri, 29 Jan 1999, Eric van Dijken wrote:
>
> > I'am trying to add Compaq SMART Raid controller support to the Redhat 5.2
> > installation.
> >
> > The PCI probing is working.
> > The module get loaded.
> > fdisk start just fine.
> > When i sel
Hello Benno,
On Fri, 29 Jan 1999, Benno Senoner wrote:
> Martin Bene wrote:
> > At 16:17 29.01.99 +0100, you wrote:
> > >assume I set up LILO to load the kernel off the first disk (where the
> > >/boot dir resides too)
> > >
> > >when the first disk crashes , the system won't boot anymor
I have also noticed this type of problem. It seems as though the RAID5
driver generates a growing write backlog and keeps allocating new
buffers when new asynchronous write requests get in. Eventually it
reserves all the available physical memory. Trying to swap data to
virtual memory storage wou
On Fri, 29 Jan 1999, Eric van Dijken wrote:
> I'am trying to add Compaq SMART Raid controller support to the Redhat 5.2
> installation.
>
> The PCI probing is working.
> The module get loaded.
> fdisk start just fine.
> When i select "Done" i get an Signal 11, i can't find out where this
> happe
How about booting off the network, from another system already deemed
reliable. Most network cards just need a bootrom to be plugged in, I think
some of the intel motherboards with integrated eepro are boot-capable.
I suppose you could have a network of raid5 machines all set up this way,
and pre
| but do you think that there is a possibility that the disk gets corrupted at a
| point which,
| LILO begins loading itself (prior kernel loading) and then stops due to disk I/O
| error ?
usually the whole disk will just fail first.
how about a compromise here: do the LILO thing (since it's no
>
> >In this case the bootfloppy has the advantage that if it is corrupt you can
> >quickly replace it with a new.
>
> This is why you'd have entries for all the disks in the lilo config files.
> You'd use lablel like Linux_d1, Linux_d2 ... or whatever. If loading the
> image from the first disk f
At 18:14 29.01.99 +0100, you wrote:
>thanks, I thought about this option too:
>
>but assume the worst of the worst:
>
>LILO starts on the first disk, and then tries to read the kernel image from
>the harddisk, but at this point the BIOS encounters a buggy sector and can
not >complete the loading o
Martin Bene wrote:
> At 16:17 29.01.99 +0100, you wrote:
> >
> >assume I set up LILO to load the kernel off the first disk (where the
> >/boot dir resides too)
> >
> >when the first disk crashes , the system won't boot anymore.
> >Solution:
>
> have a /boot1 ... /bootn on each of your disks; make
At 16:17 29.01.99 +0100, you wrote:
>
>assume I set up LILO to load the kernel off the first disk (where the
>/boot dir resides too)
>
>when the first disk crashes , the system won't boot anymore.
>Solution:
have a /boot1 ... /bootn on each of your disks; make each disk bootable.
You'll need one
Hello,
I was looking for the most crashproof setup of a Software Root-RAID
array:
my conclusion:
assume one wants to setup a machine with Root RAID5 array,
the problem is the booting of the kernel,
since LILO uses the BIOS routines the kernel must reside on a standard
partition (non software-r
m. allan noah wrote:
> the eide electrical interface does not support hot-swap. i have done
> hot-remove many times, but not hot-add. seems like a nice way to lose a
> drive.
I tested the following:
Redhat 5.2 kernel 2.0.36 + raid 0145 + raidtools 0.90
RAID5 setup consisting of 3 partitions: /
Hi,
I'am trying to add Compaq SMART Raid controller support to the Redhat 5.2
installation.
The PCI probing is working.
The module get loaded.
fdisk start just fine.
When i select "Done" i get an Signal 11, i can't find out where this
happens.
Anybody got a clue ?
Greetings, Eric.
> You need to start using data at cylinder 1 on all disks or it will get
> nuked. It doesn't happen on the first disk because ext2 skips some
> space at the beginning of the volume.
>
> Swap space has the same problem, you cannot start it at cyliner 0.
> So if RAID adds a workaround for it, the
22 matches
Mail list logo
