> If the partition types are set to "fd" and you selected the "autorun"
> config option in block devices (it should be turned on on a rawhide-type
> kernel), raidstart shouldn't be necessary. (the kernel will have
> already started the md arrays itself, and the later initscripts raidstart
> call
> How about --force / -f look for $HOME/.md_force_warning_read and
>
> if not exists:
> - print huge warning (and beep thousands of times as desired)
> - creat()/close() the file
how about an expiration on the timestamp on this file
ie: if the time is longer than 2 weeks make them read it again
> -Original Message-
> From: Martin Eriksson [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, March 18, 2000 4:14 AM
> To: [EMAIL PROTECTED]
> Subject: How to get RAID (0) working in kernel 2.2.14 & 2.3.47 ?
>
> Hi!
>
> I've installed my system with the RH6.1 installation process
> to be a
[ Saturday, March 18, 2000 ] Brian Lavender wrote:
> I am trying to apply the raid patch to the 2.2.14 kernel
> and I get this error. What is wrong?
1) Great reason to use --dry-run with patch so you can spot
possible problems before writing to you source tree.
> everest:/usr/src/linux# patc
Jakob Østergaard wrote:
>
> Someone (Probably Andre Hedrick, or perhaps Andrea Arcangali -- sorry guys, I
> don't recall) explained this on LKML. Out of my memory it has something to do
> with ATA modes and the kernel configuration. You haven't enabled ``Generic
> busmaster support'', or perhaps
Hi,
I have set up raid1 for my system. I have a seperate hard disk for
root and boot, and two hds attached to promise ultra 66 - /dev/hde and
/dev/hdg. Their partitions are fd (raid autodetect)
on issuing mkraid, I get
handling MD device /dev/md0
analyzing super-block
disk 0: /dev/hde1, 1331212
> Pick up lilo-21.3 - I have it here, if you can't find it. Perhaps Ingo
> could place it together with the raid-patches so there would be somewhere
> centralized - or going back to kernel.org - opinions, Jakob?
I found lilo-21.14 on debian unstable. Any hint?
Luigi Gangitano
ICQ: 2406003
WWW:
Hi!
I've installed my system with the RH6.1 installation process to be a small
boot partition, a small swap part., a bigger raid0 swap part and a really
big raid0 root partition.
Now this is with kernel 2.2.12-20, and the system uses an initrd to load the
raid0 module.
When I try to upgrade to
> -Original Message-
> From: Luca Berra [mailto:[EMAIL PROTECTED]]
> Sent: Friday, March 17, 2000 5:02 AM
> To: Linux Raid list (E-mail)
> Subject: Re: upgrade from 2.2.12-20 to 2.2.14 breaks stuff
>
>
> On Wed, Mar 15, 2000 at 12:40:07PM -0800, Gregory Leblanc wrote:
> > The patch appli
I am trying to apply the raid patch to the 2.2.14 kernel
and I get this error. What is wrong?
brian
everest:/usr/src/linux# patch -p1 < raid-2.2.14-B1.patch
patching file `init/main.c'
Hunk #2 FAILED at 488.
Hunk #3 succeeded at 940 with fuzz 2 (offset 12 lines).
Hunk #4 FAILED at 1438.
2 out of
Hi,
I have mount handly raid on 2.2.12. it works fine :)
The problem is: how to make a fsck on start, usually done
on /dev/sda1 etc, because it does not want to make
a fsck on /dev/md0 :(
At the moment I have the /etc/fstab to not allow the check
but it is not a good solution I think.
Thanks
Octa
On Fri, 17 Mar 2000, Christian Robottom Reis wrote:
> On Wed, 15 Mar 2000, Luigi Gangitano wrote:
>
> > I need some help setting up boot on a RAID1 device. I used Method 2 of
> > Jakob OEstergaard's latest HowTo. I got it working, now my system mounts
> > /dev/md0 as root partition. But if I
On Tue, 14 Mar 2000, Scott M. Ransom wrote:
> Hello,
>
> I have just set up RAID0 with two 30G DiamondMax (Maxtor) ATA-66 drives
> connected to a Promise Ultra66 controller.
>
> I am using raid 0.90 in kernel 2.3.51 on a dual PII-450 with 256M RAM.
>
> Here are the results from bonnie:
>
>
[ Wednesday, March 15, 2000 ] root wrote:
> > mkraid --**-force /dev/md0
/me attempts to get the Stupid Idea Of The Month award
Motivation: trying to keep the Sekret Flag a secret is a failed effort
(the number of linux-raid archives, esp. those that are searchable, make
this a given), and a
On Wed, 15 Mar 2000, Luigi Gangitano wrote:
> I need some help setting up boot on a RAID1 device. I used Method 2 of
> Jakob OEstergaard's latest HowTo. I got it working, now my system mounts
> /dev/md0 as root partition. But if I try to update LILO (to make it working on
> the second hd's MB
I figured out why the raid-2.2.14-B1 patch from
http://www.redhat.com/~mingo would fail. I went to the
web page with lynx, and I hit 'p' for print which gives
you the option to print to a file. The print option must
have mangled the patch, because later, I hit 'd' for
download, and it worked!
$
On Wed, 15 Mar 2000 [EMAIL PROTECTED] wrote:
> > Can you please tell me where can I find the latest raid-tools? I
> found raidtools- > dangerous on http://people.redhat.com/mingo and
> didn't try to use it.
>
> Good question. From my impression, Linux (software) raid support got
> a bit divided
Dear all,
I am running raidtools 0.90.990824-5 on a mingo-B1-patched 2.2.14 for
quite some time. Now a few days ago the machine just froze (no keyboard,
no login, no remote login, ping worked, that's all) and had to be
resetted. It came up fine, reconstructed etc. but there is really not a
single
> "Kent" == Kent Nilsen <[EMAIL PROTECTED]> writes:
Kent> I've got exactly the same problem on a Mylex hardware RAID-
Kent> controller, writing is nearly twice as fast as reading. The
Kent> drives are Barracuda 50Gb drives, the controller is a
Kent> DAC1164P. I use the latest firmware, and la
On Tue, 14 Mar 2000, Malcolm Beattie wrote:
> Benchmarking it on a stripeset of 7 x 9GB disks on a Ultra3 bus with
> one of the Adaptec 7899 channels, it's impressively fast. 81MB/s block
> reads and 512 seeks/s in bonnie and 50MB/s (500 "netbench" Mbits/sec)
> running dbench with 128 threads. I'
20 matches
Mail list logo
