From owner-freebsd-questions Mon Nov 1 10: 6:32 1999 Delivered-To: freebsd-questions@freebsd.org Received: from yana.lemis.com (yana.lemis.com [192.109.197.140]) by hub.freebsd.org (Postfix) with ESMTP id 3BDCB152B1 for ; Mon, 1 Nov 1999 10:06:21 -0800 (PST) (envelope-from grog@lemis.com) Received: from mojave.sitaranetworks.com ([199.103.141.157]) by yana.lemis.com (8.8.8/8.8.8) with ESMTP id EAA29840; Tue, 2 Nov 1999 04:36:15 +1030 (CST) (envelope-from grog@lemis.com) Message-ID: <19991101120441.40752@mojave.sitaranetworks.com> Date: Mon, 1 Nov 1999 12:04:41 -0500 From: Greg Lehey To: Alfred Perlstein , Greg Skouby Cc: freebsd-questions@FreeBSD.ORG Subject: Re: vinum RAID-5 again Reply-To: Greg Lehey References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: ; from Alfred Perlstein on Mon, Nov 01, 1999 at 12:00:00AM -0800 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 1 November 1999 at 0:00:00 -0800, Alfred Perlstein wrote: > On Mon, 1 Nov 1999, Greg Skouby wrote: > >> Hello, >> I got this sample RAID-5 config off of lemis.com/vinum and it >> seems over simplified to the point where I don't think I understand it. If >> at any time in this message you think I need to go back and RTFM please >> stop reading and let me know that. This is the sample config for RAID-5 >> that I am referring to: >> >> drive e device /dev/da6h >> volume raid5 >> plex org raid5 512k >> sd length 128m drive a >> sd length 128m drive b >> sd length 128m drive c >> sd length 128m drive d >> sd length 128m drive e >> >> >> I have a couple of questions about this. Is this config only slicing up >> one drive? That is what I gather from the config but the theory behind >> RAID-5 is that you need at least 3 for there to be a point in using >> RAID-5. So one of my many questions is that where do the drive a, drive b, >> drive c, drive d, and drive e 's come from? Are there seperated >> statements for those devices like there is for the drive e? Something such >> as drive a devide /dev/da0h? > > I think there is an implied > > drive a device /dev/da2h > drive b device /dev/da3h > drive c device /dev/da4h > drive d device /dev/da5h > > before the "drive e device /dev/da6h" line. > > it should be noted that some of the shortcuts used in the vinum manpage > that aren't noted as being shortcuts can make things confusing for the > first time user. > > the "drive" commands just provide a meaningful alias to /dev/ entries. In particular, it allows you to move drives around physically. Vinum will still find them when starting up, thus removing a potential way of shooting yourself in the foot. Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message