From owner-freebsd-questions Sun Mar 7 21: 2:46 1999 Delivered-To: freebsd-questions@freebsd.org Received: from inet.chip-web.com (c1003518-a.plstn1.sfba.home.com [24.1.82.47]) by hub.freebsd.org (Postfix) with SMTP id 7812014DE9 for ; Sun, 7 Mar 1999 21:02:21 -0800 (PST) (envelope-from ludwigp@bigfoot.com) Received: (qmail 17793 invoked from network); 8 Mar 1999 05:02:03 -0000 Received: from speedy.chip-web.com (HELO speedy) (172.16.1.1) by inet.chip-web.com with SMTP; 8 Mar 1999 05:02:03 -0000 Message-Id: <4.1.19990307205103.00a42670@mail-r> X-Sender: ludwigp@mail-r X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sun, 07 Mar 1999 21:02:00 -0800 To: Laurence Berland , Greg Lehey From: Ludwig Pummer Subject: Re: vinum (how to use after creation) Cc: freebsd-questions@FreeBSD.ORG In-Reply-To: <36E34FBD.CB05405A@confusion.net> References: <199903071254.MAA02531@franklin.matlink> <4.1.19990307101720.00c13100@mail-r> <19990308143012.M490@lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You didn't need to send your message twice. At 08:19 PM 3/7/99 , Laurence Berland wrote: >Can someone get a little bit more in depth on the different kinds of plexes? > I'm not >quite clear what the differences are. I'll present simplified examples, but they should be enough for you to get the general idea. > concatenated plexes use the complete address space of each subdisk in >turn. That means that the first subdisk has the first X megabytes of the plex, the next subdisk has the next Y megabytes, etc. up to the total size of the plex. > A striped plex conforms to RAID 0. The address space is taken from each >subdisk >in turn in stripes of a specified size. This makes for more even loading in > many cases. If you've got 2 subdisks, then 1 subdisk has half of the plex, and the other had the other half. The data is "interleaved," meaning that that instead of having the first half of the plex on one drive, every other megabyte is on the first drive, and the 'other' every other megabyte is on the second drive. > A RAID 5 plex incorporates error recovery: if each subdisk is located on a >different physical drive, the plex can continue operation even if any single >drive > involved in the plex fails. IIRC, RAID 5 involves striping + parity. For a 3 subdisk configuration, data is striped between the first two subdisks. The subdisk drive holds parity information for every bit contained on the first two subdisks. A '1' bit on the third subdisk means that the corresponding bits on the first two subdisks are the same, and a '0' means that they are different. So, if any one subdisk goes down, it can later be recreated from the other two. I'll let Greg correct any mistakes I've made... --Ludwig Pummer ( ludwigp@bigfoot.com ) ICQ UIN: 692441 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message