On Thu, 27 Jul 2000, Art wrote:
> After pulling out one disk (system off line), it came back on line with the
> data intact... It started automatically the reconfiguration using the spare
> disk.
> The funny thing was, after reinserting the original disk it did not
> reconfigure it automatially.
G'day Folks,
My apologies if this is RTFM or previously discussed on list (I have
just joined).
We have implemenetd mirroring using raidtools 0.9 on RedHat 6.2.
It is working well, but we would like the ability to do the following to
backup a Lotus Domino server:
1. Shutdown Domino server
2. d
> -Original Message-
> From: Neil Brown [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, July 26, 2000 7:41 PM
> To: Anton
> Cc: [EMAIL PROTECTED]
> Subject: Re: raid and 2.4 kernels
>
> On Wednesday July 26, [EMAIL PROTECTED] wrote:
> > do the kernel developers responsible for RAID read thi
On Wednesday July 26, [EMAIL PROTECTED] wrote:
> do the kernel developers responsible for RAID read this list? I would be
> interested in seeing some constructive discussion about the reports of
> degraded RAID performance in the 2.4 kernels. It is particularly
> disappointing given that SMP app
Take a look at
http://metalab.unc.edu/mdw/HOWTO/Software-RAID-HOWTO-4.html#ss4.11
There is a patched version of LILO wich accept boot=/dev/md0 in
lilo.conf and will make each disk in the mirror bootable.
Ilia Baldine a écrit :
> set boot to a real bootable device (like /dev/sda) and root to the
Art <[EMAIL PROTECTED]> said:
> Dear Raiders,
>
> I installed a 2.2.16 kernel over my Suse 6.3 (2.2.13) and patched them with
> raid-2.2.16-A0.txt.
> Installation of the raidtools-19990824-0.90.tar.gz , which is by the way the
> same as raidtools-dangerous-0.90-2116.tar.gz (I checked, but ma
Dear Raiders,
I installed a 2.2.16 kernel over my Suse 6.3 (2.2.13) and patched them with
raid-2.2.16-A0.txt.
Installation of the raidtools-19990824-0.90.tar.gz , which is by the way the
same as raidtools-dangerous-0.90-2116.tar.gz (I checked, but maybe not
good enough), was a piece of cake.
On Wed, 26 Jul 2000, Bryan Batchelder wrote:
> I've been wanting to mess around with the latest 2.4 kernels and RAID, but
> one thing that I just don't understand/know about the whole compiling the
> kernel is this: How do you manage the System.map file that resides in
> /boot on RedHat systems
On Wed, 26 Jul 2000, Anton wrote:
> do the kernel developers responsible for RAID read this list? I would be
> interested in seeing some constructive discussion about the reports of
> degraded RAID performance in the 2.4 kernels. It is particularly
> disappointing given that SMP appears to be a
InterNETACTIVE has sold for $39.95 and more...
InterNETACTIVE allows you to post your ad on
Classified Sites and Internet Malls for free!
InterNETACTIVE reveals what REALLY works to get
you top ranking among the most popular search
engines.
InterNETACTIVE is yours FREE with no strings
attached!
I am sure each individual has their own style for rolling kernels, but on
redhat systems my preference is after running "make config", edit the
Makefile. I tweekt the "EXTRAVERSION" variable towards the top so I can
have multiple kernels/module versions of the same revision (ex 2.2.16-1
2.2.16-2
Title: OT: Kernel Management
I've been wanting to mess around with the latest 2.4 kernels and RAID, but one thing that I just don't understand/know about the whole compiling the kernel is this: How do you manage the System.map file that resides in /boot on RedHat systems?
I have no problems
do the kernel developers responsible for RAID read this list? I would be
interested in seeing some constructive discussion about the reports of
degraded RAID performance in the 2.4 kernels. It is particularly
disappointing given that SMP appears to be a lot better in 2.4 vs 2.2
--
ai
http:/
I found this patch also (directed to it via the HOWTO)... is it possible
to post Ingo's patches to the kernel.org ftp sites?
donfede
On Wed, 26 Jul 2000, Nic Benders wrote:
> I used Ingo's patch from
> http://people.redhat.com/mingo/raid-patches/raid-2.2.16-A0
> and it built without iss
I used Ingo's patch from
http://people.redhat.com/mingo/raid-patches/raid-2.2.16-A0
and it built without issue. There is also a 2.2.17 patch that applies
cleanly against the Alan Cox's 2.2.17pre13 code for me.
-Nic Benders
On Wed, 26 Jul 2000, Reid Sutherland wrote:
> Does anyone have
Hello,
Does anyone have a patch that will patch properly for 2.2.16?
I've looked on kernel.org/pub/linux/daemons/raid/alpha but found only
2.2.12 patches and nothing later.
Thank you.
-reid
set boot to a real bootable device (like /dev/sda) and root to the
md device.
-ilia
"Gabor Z. Papp" wrote:
Hello all,
what is the correct root/boot LILO config option for RAID1?
(root fs on raid)
Seems boot=/dev/md0 and root=/dev/md0 OK, but LILO can't
boot only when I issue manually the 'kernel
> what is the correct root/boot LILO config option for RAID1?
> (root fs on raid)
> Seems boot=/dev/md0 and root=/dev/md0 OK, but LILO can't
> boot only when I issue manually the 'kernel root=/dev/md0'
Hi,
try linear
# cat /etc/lilo.conf
[...]
linear
[...]
Octave
Amicalement,
oCtAvE
"Inter
Hello all,
what is the correct root/boot LILO config option for RAID1?
(root fs on raid)
Seems boot=/dev/md0 and root=/dev/md0 OK, but LILO can't
boot only when I issue manually the 'kernel root=/dev/md0'
> Mkraid aborted, the the syslog or /proc/mdstat for potential clues.
I had this promlem because of unpatched kernel.
I'm using Suse Linux 6.4.
I want to install a raid1 on /dev/hda4 and /dev/hdb2.
The /etc/raidtab is OK.
Now I want to excecute mkraid /dev/md0
The answer is:
Handling MD Device /dev/md0
analyzing super-block
disk0: ..
disk1: ..
Mkraid aborted, the the syslog or /proc/mdstat for poten
21 matches
Mail list logo
