So i guess it would be better to have the root in a different partition
and the data that are likely to change in a other partition, and that
partition i would mirror it.
I hope my backup tapes are working ;))
Lucci
=========================================
+ BRN -- Brasil Networks +
+ Lucio Godoy -- http://www.brn.co.uk +
+ mailto:[EMAIL PROTECTED] +
=========================================
On Mon, 8 Feb 1999, Alvin Starr wrote:
> On Mon, 8 Feb 1999, steve rader wrote:
>
> > > From: Lucio Godoy
> > > I would like to setup raid1 on my system as follow:
> > > Hda is partitioned as follow:
> > > hda1 /swap
> > > hda2 /
> > > and HDC is partitioned the same way, both disks are the same size and
> > > make.
> > > I like to mirror /dev/hda2 on /dev/hdc2
> >
> > Are you really sure?! =;)
> >
> > I've done a fair bit of investigation into mirroring root and
> > it's certainly not for the faint at heart. No offense to the
> > fine code warrors on this list, but I don't think mirroring root
> > is super ready for prime time yet. But, gee, I can't think
> > of *any* Unix that has a very good implementation of software
> Sun is capable of mirrioring the root file system. It although is only
> raid1 you cannot have a raid5 root.
> > mirroring of root. (Maybe the newest AIX?)
> >
> > Martin Bene <[EMAIL PROTECTED]> has a recipe that appears to be
> > "workable" with slackware. See the email archive msg
> > from Feb 5th 1999 with Subject "Re: RAID1 on / for RH 5.2"
> >
> [snip]
>
> I have been running a root raid system for a while now.
>
> using the .90 patches with the auto-initialization features it is possible
> to get a system to boot up and mount root on /dev/md0. There are 2
> problems at this time:
> 1) you cannot create a raid partition from a non raid partition. So you
> end up having to use an extra disk or partition to create the system.
> 2) lilo or other boot loaders may have some problems with booting from a
> list of drives. So that if the main disk is un-bootable a secondary
> disk will be used to boot from. This is in some ways less an issue with
> lilo and more an issue with the BIOS.
>
> Alvin Starr || voice: (416)585-9971
> Interlink Connectivity || fax: (416)585-9974
> [EMAIL PROTECTED] ||
>
>
