Date: Mon, 16 Dec 2013 20:18:14 +0000 From: "Teske, Devin" <Devin.Teske@fisglobal.com> To: Adam McDougall <mcdouga9@egr.msu.edu> Cc: "stable@FreeBSD.org" <stable@FreeBSD.org>, Devin Teske <dteske@freebsd.org>, "Teske, Devin" <Devin.Teske@fisglobal.com> Subject: Re: bsdinstall, zfs booting, gpt partition order suitable for volume expansion Message-ID: <73E28A82-E9FE-4B25-8CE6-8B0543183E7F@fisglobal.com> In-Reply-To: <2D40298B-39FA-4BA9-9AC2-6006AA0E0C9C@fisglobal.com> References: <20131210175323.GB1728@egr.msu.edu> <93C924DB-E760-4830-B5E2-3A20160AD322@fisglobal.com> <2D40298B-39FA-4BA9-9AC2-6006AA0E0C9C@fisglobal.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Dec 14, 2013, at 7:44 PM, Teske, Devin wrote: >=20 > On Dec 10, 2013, at 11:00 AM, Devin Teske wrote: >=20 >>=20 >> On Dec 10, 2013, at 9:53 AM, Adam McDougall wrote: >>=20 >>> I was wondering if either the default gpt partition order could become >>> p1=3Dboot, p2=3Dswap, p3=3Dzpool, or if the installer could be enhanced= at >>> some point to allow the user to select the order. It seems like it wou= ld >>> be easier to expand the size of the raw device (VM, iscsi, etc) and exp= and >>> the zpool if it is the last partition. I am not in a hurry to get this >>> solved, but if a change to the default order is worthwhile, it seems li= ke >>> before 10.0 would be a good time to set precedent. I'm trying to think= ahead >>> where people will be installing 10 to VMs or expandable volumes so they= can >>> take advantage of expansion with less hassle. I pinged Allen Jude on t= his >>> briefly, I think he said it used to be that way but it was changed to >>> accomodate MBR partitioning (I think, apologies for not remembering det= ails). >>=20 >> Excellent idea. Let me put that into a patch. I'll let you know when I h= ave >> something that tests clean. >=20 > GPT proved trivial. > MBR on the other hand... that proved challenging. >=20 > While trying to best that challenge... I uncovered more than a couple nas= ty bugs > while iterating over every possible combination in the installer. >=20 > That being said... I'm coming out of the "tunnel" since you sent this e-m= ail and > will soon have something to commit that implements this suggestion while = at > the same time, plugging a few edge-cases. Alrighty-then... time to share... Here's the commit that does what you want... http://svnweb.freebsd.org/base?view=3Drevision&revision=3D259476 But just keep in-mind that the whole ball of wax that I "tested to death" is actually a combination of the following (in order): http://svnweb.freebsd.org/base?view=3Drevision&revision=3D259468 http://svnweb.freebsd.org/base?view=3Drevision&revision=3D259469 http://svnweb.freebsd.org/base?view=3Drevision&revision=3D259470 http://svnweb.freebsd.org/base?view=3Drevision&revision=3D259472 http://svnweb.freebsd.org/base?view=3Drevision&revision=3D259474 http://svnweb.freebsd.org/base?view=3Drevision&revision=3D259476 http://svnweb.freebsd.org/base?view=3Drevision&revision=3D259477 http://svnweb.freebsd.org/base?view=3Drevision&revision=3D259478 http://svnweb.freebsd.org/base?view=3Drevision&revision=3D259479 http://svnweb.freebsd.org/base?view=3Drevision&revision=3D259480 http://svnweb.freebsd.org/base?view=3Drevision&revision=3D259481 Needless to say, I'm going to take that break now. --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?73E28A82-E9FE-4B25-8CE6-8B0543183E7F>