From owner-freebsd-net@FreeBSD.ORG Thu Dec 18 16:43:00 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 EDA94E1A for ; Thu, 18 Dec 2014 16:43:00 +0000 (UTC) Received: from acipenser.esturion.net (acipenser.esturion.net [65.101.5.252]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BEBFF17F0 for ; Thu, 18 Dec 2014 16:43:00 +0000 (UTC) Received: by acipenser.esturion.net (Postfix, from userid 112) id 28ECD260339; Thu, 18 Dec 2014 09:42:53 -0700 (MST) X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on acipenser.esturion.net X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham autolearn_force=no version=3.4.0 Received: from feyerabend.n1.pinyon.org (quine.pinyon.org [65.101.5.249]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by acipenser.esturion.net (Postfix) with ESMTPSA id DDDF72600CE for ; Thu, 18 Dec 2014 09:42:50 -0700 (MST) Message-ID: <5493040A.6040209@pinyon.org> Date: Thu, 18 Dec 2014 09:42:50 -0700 From: "Russell L. Carter" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: Re: compiling on nfs directories References: <1480362493.14973677.1418857654052.JavaMail.root@uoguelph.ca> <54922412.6090903@pinyon.org> <54922E49.4050906@egr.msu.edu> <549233E2.7050009@pinyon.org> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit 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 16:43:01 -0000 On 12/18/14 08:37, Adam Vande More wrote: > On Thu, Dec 18, 2014 at 9:29 AM, Alan Somers wrote: >> >> 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 > > > Using a flash drive or temporary drive seems like a much more comprehensive > test as you can fully eliminate ZFS from the picture. Which is the point > of the exercise. > Ok, good suggestions, noted, and thanks! Unfortunately I'm going to have to pick this up when I get back. Russell