Date: Wed, 23 Aug 2000 10:38:02 -0500 From: "J. Seth Henry" <jshenry@net-noise.com> To: <questions@FreeBSD.org> Subject: re: vinum preparation Message-ID: <002801c00d18$206e4e50$0e01a8c0@guinevere>
next in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format. ------=_NextPart_000_0025_01C00CEE.366CE5B0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sorry for the delay, I've been playing with the kernel configuration as well. I was able to successfully create a stripe set using the following: "/etc/vinum.conf" > drive subdisk1 device /dev/da1s1e drive subdisk2 device /dev/da2s1e drive subdisk3 device /dev/da3s1e drive subdisk4 device /dev/da4s1e drive subdisk5 device /dev/da5s1e drive subdisk6 device /dev/da6s1e volume mmvolc plex org striped 1024b sd length 2033m drive subdisk1 sd length 2033m drive subdisk2 sd length 2033m drive subdisk3 sd length 2033m drive subdisk4 sd length 2033m drive subdisk5 sd length 2033m drive subdisk6 < However, when I try to create a RAID5 array, I get an error that one of = the plexes doesn't have enough subdisks and there are two plexes, mmvolc.p0 = and mmvolc.p1, rather than just the one plex, mmvolc.p0. I simply changed the plex line to read "plex org raid5 1024b" The volumes are partitioned to fill the entire space (dangerously = dedicated) and I created equal slices of 4165120 blocks on each disk. The leftover space was left unallocated. I would prefer the safety factor of a RAID array, given that these are = old disks, so this is a bit problematic. Any help would be appreciated. I am still migrating from Linux, which is why I've been playing with the kernel. I need EXT2 support for a little while. Once I get the data on = those volumes moved around and backed up again, I will supply the create log from vinum. Thanks, Seth Henry jshenry@net-noise.com ----- Original Message ----- From: "Greg Lehey" <grog@lemis.com> To: "J. Seth Henry" <jshenry@net-noise.com> Cc: <questions@FreeBSD.ORG> Sent: Thursday, August 17, 2000 7:41 PM Subject: Re: vinum preparation > [Format recovered--see http://www.lemis.com/email/email-format.html] > > Please don't write one line per paragraph. > > On Thursday, 17 August 2000 at 10:21:39 -0500, J. Seth Henry wrote: > > I have a pile of 2Gb (more or less) SCSI hard disks laying around > > that I would like to bolt together into a RAID5 array using > > vinum. The trick is, all of the drives have slightly different = sizes, > > varying from 2033Mb to 2048Mb. I know that the subvolumes have to be > > exactly the same size, but is that the partition, or the slice? > > No. > > > I currently have them all dangerously dedicated to the full size of > > the drive, and I set the slices to be the same size. > > > > I have read all of the documentation I could get my hands on > > regarding vinum, but so far, I've found nothing that covers > > this. When I try to start the array, three of the disks come online, > > but the other three fail due to a size mismatch. From this, I would > > assume the partitions must be equally sized and the slices set to > > fill the partitions. > > No, this isn't correct. Your subdisks need to be the same size, but > Vinum should automatically trim the ones which are too large. Please > show (without mutilating the text!) the output from 'vinum create'. > > 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 ------=_NextPart_000_0025_01C00CEE.366CE5B0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 5.50.4134.600" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV>Sorry for the delay, I've been playing with the kernel = configuration=20 as<BR>well.<BR><BR>I was able to successfully create a stripe set using = the=20 following:<BR><BR>"/etc/vinum.conf"<BR>><BR>drive subdisk1 device=20 /dev/da1s1e<BR>drive subdisk2 device /dev/da2s1e<BR>drive subdisk3 = device=20 /dev/da3s1e<BR>drive subdisk4 device /dev/da4s1e<BR>drive subdisk5 = device=20 /dev/da5s1e<BR>drive subdisk6 device /dev/da6s1e<BR><BR>volume = mmvolc<BR>plex=20 org striped 1024b<BR>sd length 2033m drive subdisk1<BR>sd length 2033m = drive=20 subdisk2<BR>sd length 2033m drive subdisk3<BR>sd length 2033m drive=20 subdisk4<BR>sd length 2033m drive subdisk5<BR>sd length 2033m drive=20 subdisk6<BR><<BR><BR>However, when I try to create a RAID5 array, I = get an=20 error that one of the<BR>plexes doesn't have enough subdisks and there = are two=20 plexes, mmvolc.p0 and<BR>mmvolc.p1, rather than just the one plex,=20 mmvolc.p0.<BR><BR>I simply changed the plex line to read "plex org raid5 = 1024b"<BR><BR>The volumes are partitioned to fill the entire space = (dangerously=20 dedicated)<BR>and I created equal slices of 4165120 blocks on each disk. = The=20 leftover<BR>space was left unallocated.<BR><BR>I would prefer the safety = factor=20 of a RAID array, given that these are old<BR>disks, so this is a bit=20 problematic. Any help would be appreciated.<BR><BR>I am still migrating = from=20 Linux, which is why I've been playing with the<BR>kernel. I need EXT2 = support=20 for a little while. Once I get the data on those<BR>volumes moved around = and=20 backed up again, I will supply the create<BR>log from=20 vinum.<BR><BR>Thanks,<BR>Seth Henry<BR><A=20 href=3D"mailto:jshenry@net-noise.com">jshenry@net-noise.com</A><BR><BR><B= R><BR><BR>-----=20 Original Message -----<BR>From: "Greg Lehey" <<A=20 href=3D"mailto:grog@lemis.com">grog@lemis.com</A>><BR>To: "J. Seth = Henry"=20 <<A = href=3D"mailto:jshenry@net-noise.com">jshenry@net-noise.com</A>><BR>Cc= :=20 <<A=20 href=3D"mailto:questions@FreeBSD.ORG">questions@FreeBSD.ORG</A>><BR>Se= nt:=20 Thursday, August 17, 2000 7:41 PM<BR>Subject: Re: vinum=20 preparation<BR><BR><BR>> [Format recovered--see <A=20 href=3D"http://www.lemis.com/email/email-format.html">http://www.lemis.co= m/email/email-format.html</A>]<BR>><BR>>=20 Please don't write one line per paragraph.<BR>><BR>> On Thursday, = 17=20 August 2000 at 10:21:39 -0500, J. Seth Henry wrote:<BR>> > I have = a pile=20 of 2Gb (more or less) SCSI hard disks laying around<BR>> > that I = would=20 like to bolt together into a RAID5 array using<BR>> > vinum. The = trick is,=20 all of the drives have slightly different sizes,<BR>> > varying = from=20 2033Mb to 2048Mb. I know that the subvolumes have to be<BR>> > = exactly the=20 same size, but is that the partition, or the slice?<BR>><BR>>=20 No.<BR>><BR>> > I currently have them all dangerously dedicated = to the=20 full size of<BR>> > the drive, and I set the slices to be the same = size.<BR>> ><BR>> > I have read all of the documentation I = could get=20 my hands on<BR>> > regarding vinum, but so far, I've found nothing = that=20 covers<BR>> > this. When I try to start the array, three of the = disks come=20 online,<BR>> > but the other three fail due to a size mismatch. = From this,=20 I would<BR>> > assume the partitions must be equally sized and the = slices=20 set to<BR>> > fill the partitions.<BR>><BR>> No, this isn't=20 correct. Your subdisks need to be the same size, but<BR>> Vinum = should=20 automatically trim the ones which are too large. Please<BR>> = show=20 (without mutilating the text!) the output from 'vinum = create'.<BR>><BR>>=20 Greg<BR>> --<BR>> When replying to this message, please copy the = original=20 recipients.<BR>> For more information, see <A=20 href=3D"http://www.lemis.com/questions.html">http://www.lemis.com/questio= ns.html</A><BR>>=20 Finger <A href=3D"mailto:grog@lemis.com">grog@lemis.com</A> for PGP = public=20 key<BR>> See complete headers for address and phone=20 numbers<BR><BR></DIV></BODY></HTML> ------=_NextPart_000_0025_01C00CEE.366CE5B0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?002801c00d18$206e4e50$0e01a8c0>