From owner-freebsd-net@FreeBSD.ORG Thu Dec 18 15:37:31 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 70AC46D7; Thu, 18 Dec 2014 15:37:31 +0000 (UTC) Received: from mail-pa0-x233.google.com (mail-pa0-x233.google.com [IPv6:2607:f8b0:400e:c03::233]) (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 3CFAF2BC4; Thu, 18 Dec 2014 15:37:31 +0000 (UTC) Received: by mail-pa0-f51.google.com with SMTP id ey11so1605454pad.24; Thu, 18 Dec 2014 07:37:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=lhwPQjw7Nyy2cUny7U0cbAzqvyoH9u8avv8JjXDjfAg=; b=YnOvb8aV4LywS5PAYyl512UzSrWMVTiuKPc2Dle4N+0zRu275jZc7P8sFMD+A2Kdz0 BS0gz+PvGdWjRRU9Ft4TYEtcd8ALHsijPL9iqctpB9RKY3lBGdhClVbCSaX4tX9nbqf8 tDua1ss2xM2YNxumb4VJQmagaGPgt1puIfDE7uWQ+G82jgQRZHEm+fD4h4F1p7hQddHM Kkc47U/hCOSDNyN927LqPwYgu11tHbhOjGf8SBw8/QZyl20anByKFSvZZ8M27FXybIS2 U9qavFNI5TlGu4zI6nvwViKHjebQvY2R4gjWpSHlLtf4sZZapJCVMzYZXYyk3jO5ioMQ EZSg== MIME-Version: 1.0 X-Received: by 10.70.118.202 with SMTP id ko10mr4632575pdb.48.1418917050703; Thu, 18 Dec 2014 07:37:30 -0800 (PST) Received: by 10.70.94.167 with HTTP; Thu, 18 Dec 2014 07:37:30 -0800 (PST) In-Reply-To: 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 09:37:30 -0600 Message-ID: Subject: Re: compiling on nfs directories From: Adam Vande More To: Alan Somers Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "Russell L. Carter" , 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:37:31 -0000 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. -- Adam