From owner-freebsd-current@FreeBSD.ORG Mon Dec 21 17:06:54 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A0B341065672 for ; Mon, 21 Dec 2009 17:06:54 +0000 (UTC) (envelope-from kraduk@googlemail.com) Received: from mail-fx0-f218.google.com (mail-fx0-f218.google.com [209.85.220.218]) by mx1.freebsd.org (Postfix) with ESMTP id 284D48FC08 for ; Mon, 21 Dec 2009 17:06:53 +0000 (UTC) Received: by fxm10 with SMTP id 10so2412924fxm.14 for ; Mon, 21 Dec 2009 09:06:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=y7vkMHH/1gyaiQMdYsz3XvosH46EOPVLvXMkMsq2v0o=; b=sYrWh5IZn/JUEFlBLNxEOB0ITk7yt34EDKqimcvjBIkR7FMoyJKdiWyh7p5dMPjr2l AEzIxkZBz4q9dEk25GMVzzrXFylUaWWQmTkSVGSG5WooDYSOoNg8RaNrbLmkPC1yItHl J0rN11ovMEzcUzYeaZn2PiqBSvfhaFTteZd3I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=SbWaI4GTBb5G41eZS3kvxBuBMpWnnYpD992/t4hAUH4uO+4aDnO1OiWRPKxtMKUkby bVx/r6DAmiVcYhOyqBI7ic3o6r0Ptf71ibF/S373YH1tH1CPPfs+ZZA/JeaKd8LcpWPA 1g0PKOlkOP1dYVhh7pknnKGeylkLV/e3GRmjc= MIME-Version: 1.0 Received: by 10.239.188.145 with SMTP id p17mr767412hbh.175.1261415213025; Mon, 21 Dec 2009 09:06:53 -0800 (PST) In-Reply-To: <200912210728.31761.mel.flynn+fbsd.current@mailing.thruhere.net> References: <200912210600.46044.mel.flynn+fbsd.current@mailing.thruhere.net> <200912210728.31761.mel.flynn+fbsd.current@mailing.thruhere.net> Date: Mon, 21 Dec 2009 17:06:52 +0000 Message-ID: From: krad To: Mel Flynn Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@freebsd.org Subject: Re: Some notes on RootOnZFS article in wiki X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Dec 2009 17:06:54 -0000 2009/12/21 Mel Flynn > > On Monday 21 December 2009 07:03:52 krad wrote: > > 2009/12/21 Mel Flynn > > > > ng.thruhere.net> > > > > > Hi, > > > > > > yesterday went through the RootOnZFS (gpt mirror version) and here's a > > > few notes: > > > 1) You cannot use the install CD. It doesn't have a livefs and so you > can > > > never do the actual install in 2.2. The DVD will work and the USB > image. > > > I ended up using the livefs CD and the USB image, cause I didn't want > to > > > loose > > > > Maybe that procedure needs modifying a bit, but you can do its from > disk1. > > As i have. Things are a bit clumsy but it does work. > > - Using 8.0-RELEASE disc 1 amd64, 2 coasters burnt on two different > machines > with two different OS's, the Fixit option from CD/DVD kept asking for the > livefs CD, so I assume it's not on there or two different coasters had the > exact same errors. > - Livefs doesn't have /dist/8.0-RELEASE/*. > - Ejecting livefs won't work when mounted. > - umount is on CD. > - /rescue/umount is too big for space left on md0. > - libc.so.7+umount is also too big for space left on md0. > > You are using option 5 on the fixit menu arent you? As thats what i used. Its clunky as its not bash and loads of paths are not setup. Generally these days I use a usb drive with a full installation of freebsd, with all the different distos on it it might want to install So I'm curious how the 'clumsy' method works. > > > > 3) By adding the swap partitions on the two mirrored disks to > /etc/fstab > > > top > > > actually shows the sum of these as available swap. My expectation > is/was > > > that > > > the swap would be mirrored and thus I'd have only the size of one swap > > > partition. If this isn't the case, can I get by with 1 of the two since > > > they're double the intended size or should one use 2 and thus create > them > > > half > > > the intended size? > > > > No as if you loose a disk you will only have 1/2 the swap you need. > > Point taken. > > > > 4) The given mount points have sane defaults, however, I use cvs to > > > checkout > > > the ports. It would be nice to have one example where data is already > in > > > a directory tree and how one can promote it to a zfs filesystem with > > > special properties. > > > > You cant really promote something to a file system. The ideal situation > is > > you create the fs before you unpack the ports tar ball (or cvs). > Otherwise, > > rename /usr/ports (/usr/ports.old/, create the fs as desired, then rsync > > the files there (or cp, or mv). Then delete the old tree. > > Right, I was wondering if that would actually work. If I do for example: > zfs create -o compression=on zroot/usr/local/etc > > with files in there, would this result in the files being 'below' the mount > point or would they be forever lost? > -- > Mel >