From owner-freebsd-net@FreeBSD.ORG Thu Dec 18 15:29:12 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0E3C5306 for ; Thu, 18 Dec 2014 15:29:12 +0000 (UTC) Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 91A622A6E for ; Thu, 18 Dec 2014 15:29:11 +0000 (UTC) Received: by mail-wi0-f169.google.com with SMTP id r20so1960586wiv.2 for ; Thu, 18 Dec 2014 07:29:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=qtrtwHMYX1fpiEVeV+9AZjXhPDu61+A09NTC1PPQtXE=; b=WWf0YcsVqg/1Kvz7Nz1tPDlSLBiS+Kom5loqPp5CwYQLSUs0eokEi/2ofap/LrHbSa o9Kn4SWJP2ZB1DSkGY4cWoEgXVlvOQTI6INfrhyCXvNqJCk5G7Wzd6xaDMAi2GAf7UCq raMaGpMMiihcSxwGTyRl9L3tcyplBjG8iHiQSaqHywHoeyAzc+TVVfOqESqufoEr5S3N crxzRWQtacIjRmrivets0vNzrDQ/7AUxnCy9fimQJzIqfVdbcaBY3oqNGE/oKOWvD7my 1DKNKncw613peiR6iUYMVlRX1ryrJkp0QR4NBD8N73VD9vEgxq8tiB+nBsq8qoj/KPgx ToMg== MIME-Version: 1.0 X-Received: by 10.194.60.45 with SMTP id e13mr5424071wjr.109.1418916543228; Thu, 18 Dec 2014 07:29:03 -0800 (PST) Sender: asomers@gmail.com Received: by 10.194.17.129 with HTTP; Thu, 18 Dec 2014 07:29:03 -0800 (PST) In-Reply-To: <549233E2.7050009@pinyon.org> References: <1480362493.14973677.1418857654052.JavaMail.root@uoguelph.ca> <54922412.6090903@pinyon.org> <54922E49.4050906@egr.msu.edu> <549233E2.7050009@pinyon.org> Date: Thu, 18 Dec 2014 08:29:03 -0700 X-Google-Sender-Auth: uXW4h3CH2JYPdwemGOxtas5Gfzo Message-ID: Subject: Re: compiling on nfs directories From: Alan Somers To: "Russell L. Carter" Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Dec 2014 15:29:12 -0000 On Wed, Dec 17, 2014 at 6:54 PM, Russell L. Carter wrote: > > > On 12/17/14 18:30, Adam McDougall wrote: >> >> On 12/17/2014 19:47, Russell L. Carter wrote: >>> >>> >>> >>> On 12/17/14 16:07, Rick Macklem wrote: >> >> >>>> If this is using an exported ZFS volume, it would be nice if you >>>> could do the same test using an exported UFS file system, to see if >>>> this is ZFS related. >>> >>> >>> It is indeed using exported ZFS filesystems, but unfortunately I have >>> no USF filesystems available to test. >>> >>> Russell >> >> >> Can you create a zvol, newfs it with ufs and export it? > > > Maybe. I would love to help if I can, w/o disrupting my existing > carefully planned physical disk layouts. I'm a zfs novice here, do I > need free space unallocated to existing zpools, or can I shrink an > existing pool? (assuming that zfs can transmute lead into gold, with > the right incantations). I have plenty of "free" space allocated to > existing pools that span my physical drives. > > If I have to add a physical drive (that's possible, but it will be a > slow drive sitting on my shelf) then I need to wait until I get back > from holiday travels. You don't need to screw with your pools at all. A zvol is like a managed like a ZFS filesystem, except it's a block device. You can create one and mount it with a command like this: zfs create -V 8g mypool/myvol newfs [options] /dev/mypool/myvol mount /dev/mypool/myvol /mnt -Alan