Date: Mon, 1 Dec 1997 21:05:47 -0800 (PST) From: "Jamil J. Weatherbee" <jamil@trojanhorse.ml.org> To: Ian Freislich <iang@digs.iafrica.com> Cc: Satoshi Asami <asami@cs.berkeley.edu>, hackers@freebsd.org Subject: Re: Drive Mirroring Message-ID: <Pine.BSF.3.96.971201210301.194A-100000@trojanhorse.ml.org> In-Reply-To: <E0xccrm-0004EW-00@brane.digs.iafrica.com>
next in thread | previous in thread | raw e-mail | index | archive | help
The main problem has to do with the kind of people that need to be able to make the system work when it crashes. We are not talking about unix geniuses here it is just their web server and If a disk stops they want to have it replaced later without stopping the system for 24 hours to get someone knowledgeable out there to fix it. This is my main concern. And in this respect it looks like rdist might work for me but there are still some security issues I need to resolve + that rdist doesn't do continuous updates like ccd. On Mon, 1 Dec 1997, Ian Freislich wrote: > "Jamil J. Weatherbee"... > > One problem with this: If the system is rebooted with only one drive it > > crashes, second you cannot do a out of the box install on ccded drives so > > they are pretty useless tom me for anything but data. > > > > I actually tried the exact scenario you suggest. > > This doesn't really make sense to me. I know that you can't do an > install onto a ccd (which is a source of irritation for me) but I > have a number of servers at work which I have setup or helped setup > that have all of their file systems mirrored except for /. > > I'll admit it's a little laborious to setup, but it can be done. > I do a minimal install, create the ccds, copy stuff around and then > install source and the rest of the stuff that I want. > > I'm unsure why you don't want to use ccd. > > -- igf (Ian Freislich) > http://copernicus.iafrica.com/ >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.971201210301.194A-100000>