Date: Thu, 27 Nov 2008 10:54:31 -0800 From: "Peter Steele" <psteele@maxiscale.com> To: =?utf-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= <des@des.no> Cc: freebsd-hackers@freebsd.org, Mike Meyer <mwm@mired.org> Subject: RE: FreeBSD boot menu is missing Message-ID: <2ACA3DE8F9758A48B8BE2C7A847F91F240CEC4@polaris.maxiscale.com> In-Reply-To: <86myfl15cl.fsf@ds4.des.no> References: <2ACA3DE8F9758A48B8BE2C7A847F91F240CE6B@polaris.maxiscale.com><20081126153510.6062cd55@bhuda.mired.org><2ACA3DE8F9758A48B8BE2C7A847F91F240CE99@polaris.maxiscale.com><20081126190545.17b79195@bhuda.mired.org><2ACA3DE8F9758A48B8BE2C7A847F91F240CEB4@polaris.maxiscale.com><861vwx4fd5.fsf@ds4.des.no><2ACA3DE8F9758A48B8BE2C7A847F91F240CEBF@polaris.maxiscale.com> <86myfl15cl.fsf@ds4.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
>So what you do, instead, is make sure there is a little space left over >at the end of the slice that you create in the first step. Then, once >gmirror is available, you gmirror label the slice, then gmirror insert >the corresponding slice on the other disk(s), and gmirror rebuild. No >copying involved; gmirror takes care of it all. > >The key here is that 'gmirror label' is non-destructive as long as the >last sector on the provider is unused. The problem is I was unable to get multiple slices defined in a sysinstall config script. I tried many variations of parameters to pump into diskPartitionEditor and diskLabelEditor so that we could create three slices during the install but I couldn't find anything that worked. So I ended up having to create a single full disk slice to install the OS onto, and then in a post commit step slice the disks up as we want them and copy the OS over. I couldn't find a single example how to create multiple slices in a sysinstall config file. If you know how to do this, I'd love to see it. >It does, AFAIK, even on SATA, provided the controller supports it and is >configured correctly. With the proper controller and drive, yes, FreeBSD does support hot swap, to a point. Let's say for example that you have a file system mounted on a drive and that drive dies. You can pull it and put in a new one, but FreeBSD will not let you unmount the file system on the original drive. Even umount -f fails. We have to reboot to get the old mount point released, and we haven't found any way around this.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2ACA3DE8F9758A48B8BE2C7A847F91F240CEC4>