At 21:21 Uhr + 07.07.2000, Torsten Kuehn wrote:
>I received an obscure 'bad parameter' error msg with 'mdrun -p5 /dev/md0'
>(after successful 'mdadd /dev/md0 /dev/sda2 /dev/sdb1 /dev/sdc1'). Ker-
>nel error log revealed 'md: 08:02: invalid raid superblock magic (0) on block..'
>Item 1b. c) is
At 9:30 Uhr -0400 06.07.2000, Tamas Acs wrote:
>I"ve been running simulations on our RAD 1 box. I pulled out a drive
>(they're hot-swappable) and it starts reconstruction on the spare disk but
>after a while the machine hangs with scsi bus timeouts and resets.
This sounds like typical SCSI cabl
At 17:25 Uhr -0700 05.07.2000, Ben wrote:
>> So I can't get your point.
>Well, unfortunately we're using IDE drives, each connected to an IDE/SCSI
>adapter
Okay, this wasn't clear. Sorry.
>> Simply test by copying something onto it, sync, work otherwise so the
>> kernel buffers get flushed and
On Wed, 5 Jul 2000, Ben wrote:
> The drives are all connected on the same SCSI-2 bus (we care about
> quantity and reliability, not speed), which is obviously not a
> performance deamon but should work just fine.
If you care for reability, you should probably end up in using some sort
of hardwar
>> Also how big of a raid partition is possible? I have a data partition need
>> of 36 gigs plus.
I set up a 50Gig+ Stripe with the old md code with kernel 2.2.12 a few months ago - no
probs.
:wq! PoC
At 14:58 Uhr -0400 05.07.2000, Robert wrote:
>1. If a drive is not present when the machine is booted, but is inserted
>after the machine is up, it can't be mounted. (You get a message that the
>device is not a valid block device.)
You must tell the Kernel about this new device. This is also men
