From owner-freebsd-stable Wed Sep 5 17: 0:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from camelot.bitart.com (BITart-45.BITart.com [206.103.221.45]) by hub.freebsd.org (Postfix) with SMTP id 587DD37B401 for ; Wed, 5 Sep 2001 17:00:16 -0700 (PDT) Received: (qmail 1015 invoked by uid 101); 6 Sep 2001 00:00:15 -0000 Message-ID: <20010906000015.1014.qmail@camelot.bitart.com> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 4.2mach v148) In-Reply-To: <20010905181858.W63459@enteract.com> X-Nextstep-Mailer: Mail 4.2mach (Enhance 2.2p1) Received: by NeXT.Mailer (1.148) From: Gerd Knops Date: Wed, 5 Sep 2001 19:00:14 -0500 To: jim@nasby.net Subject: Re: Vinum vs. hardware RAID (was: RAID5) Cc: FreeBSD-Stable Reply-To: gerti@BITart.com References: <20010903142145.K10812-100000@topperwein.dyndns.org> <200109041749.KAA12474@mina.soco.agilent.com> <20010905084245.H85816@wantadilla.lemis.com> <20010905181858.W63459@enteract.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jim C. Nasby wrote: > > On the same vein, is booting off of vinum in the works yet? I know > it's been looked into... It seems that would be one of the biggest > advantages that hardware raid has over vinum. > For some definition of advantage that is. I always prefer to NOT have / and /usr on a RAID. If the file system gets corrupted (software bug, power/UPS failure, someone hits reset button by accident, someone snags the power cable, bit rot causes incorrect read and write back to the file system, you make a mistake and delete some important file, or a million other causes) you are dead in the water, since the RAID does it's duty and copies the flawed data to all drives. I view the / and /usr partitions as more or less static, and only put the partition containing user data on the RAID. If something important changes in / or /usr, I mirror those to the backup disk manually. Now if any of those partitions gets corrupted beyond repair (or beyond the abilities of some remote operator), I simply have to swap the drives and am back in business. I think a setup like this is actually safer. Just my $.02. Gerd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message