Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 7 Mar 2007 14:44:32 +0100
From:      Pawel Jakub Dawidek <pjd@FreeBSD.org>
To:        Joao Barros <joao.barros@gmail.com>
Cc:        freebsd-fs@freebsd.org, freebsd-current@freebsd.org
Subject:   Re: ZFS port to FreeBSD: 2nd patchset available.
Message-ID:  <20070307134432.GB2864@garage.freebsd.pl>
In-Reply-To: <70e8236f0703061916u466e8ddcxbd1980dfca0c669@mail.gmail.com>
References:  <20070304123801.GA22350@garage.freebsd.pl> <20070306005831.22fb6115.nork@FreeBSD.org> <70e8236f0703060725j3487764enffe1ad524a098c96@mail.gmail.com> <45ED9289.4090001@barryp.org> <70e8236f0703061916u466e8ddcxbd1980dfca0c669@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--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 <bp@barryp.org> 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--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070307134432.GB2864>