From owner-freebsd-fs@FreeBSD.ORG Wed Mar 7 13:46:05 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A7A4316A482; Wed, 7 Mar 2007 13:46:05 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.freebsd.org (Postfix) with ESMTP id DF06113C48D; Wed, 7 Mar 2007 13:46:04 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 19D8A45B26; Wed, 7 Mar 2007 14:46:02 +0100 (CET) Received: from localhost (p42220-ipbffx02marunouchi.tokyo.ocn.ne.jp [211.129.152.220]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 3C30F456AB; Wed, 7 Mar 2007 14:45:55 +0100 (CET) Date: Wed, 7 Mar 2007 14:44:32 +0100 From: Pawel Jakub Dawidek To: Joao Barros Message-ID: <20070307134432.GB2864@garage.freebsd.pl> References: <20070304123801.GA22350@garage.freebsd.pl> <20070306005831.22fb6115.nork@FreeBSD.org> <70e8236f0703060725j3487764enffe1ad524a098c96@mail.gmail.com> <45ED9289.4090001@barryp.org> <70e8236f0703061916u466e8ddcxbd1980dfca0c669@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="kXdP64Ggrk/fb43R" Content-Disposition: inline In-Reply-To: <70e8236f0703061916u466e8ddcxbd1980dfca0c669@mail.gmail.com> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.5 required=3.0 tests=BAYES_00,RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: ZFS port to FreeBSD: 2nd patchset available. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Mar 2007 13:46:05 -0000 --kXdP64Ggrk/fb43R Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Mar 07, 2007 at 03:16:48AM +0000, Joao Barros wrote: > On 3/6/07, Barry Pederson wrote: > >Joao Barros wrote: > > > >> After some tries I finally got it to buildworld, but at 3am I never > >> got to test anything other than 'kldload zfs' > >> > >> I was reading the man pages and I was wondering if files are supported > >> devices like in this example: > >> > >> Example 4 Creating a ZFS Storage Pool by Using Files > >> > >> The following command creates an unmirrored pool using files. While > >> not recommended, a pool based on files can be useful for experimental > >> purposes. > >> > >> # zpool create tank /path/to/file/a /path/to/file/b > >> > >> I'd have to feed some noisy disks to my machine if file devs are not > >> supported -.- > > > >I tried something like that, with a 512mb file: > > > > dd if=3D/dev/zero of=3D/tmp/foo bs=3D1048976 count=3D512 > > zpool create tank /tmp/foo > > > >but it comes back with > > > > cannot use '/dev//tmp/foo': must be a GEOM provider > > > >mdconfig is one way to go here, creating a memory disk based on that > >file. and then creating a pool from that > > > > mdconfig -a -t vnode -f /tmp/foo > > > >(comes back with "md0" perhaps, meaning it's created a /dev/md0 ) > > > > zpool create tank md0 > > > >and you should be in business. mdconfig(8) '-t vnode' is exactly the reason I ignored vdev_file. > That did the trick, thanks for the idea :) >=20 > After creating a pool, copying some files and other "just playing > around commands" I got this on my log: >=20 > ZFS filesystem version 3 > ZFS storage pool version 3 > acquiring duplicate lock of same type: "zfs:tx:cpu" [...] I know about those 'duplicate lock' and I've patches to fix this particular warning. Those are harmless. I also have LOR.txt file with LORs I know and are confirmed by SUN guys to be harmless. So for now I'd advice not to use WITNESS. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --kXdP64Ggrk/fb43R Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFF7sHAForvXbEpPzQRAmXQAJ9AjDVhIQNggL+V4Q37+vtDqduAUQCgojLZ l3RGzTOAFuXzUhjJ6k8EKIU= =B+5e -----END PGP SIGNATURE----- --kXdP64Ggrk/fb43R--