From owner-freebsd-stable@FreeBSD.ORG Mon Oct 24 10:13:12 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D02C106564A for ; Mon, 24 Oct 2011 10:13:12 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id BB4118FC14 for ; Mon, 24 Oct 2011 10:13:11 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1RIHWm-0004rK-QL for freebsd-stable@freebsd.org; Mon, 24 Oct 2011 12:13:08 +0200 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 24 Oct 2011 12:13:08 +0200 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 24 Oct 2011 12:13:08 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Ivan Voras Date: Mon, 24 Oct 2011 12:12:56 +0200 Lines: 63 Message-ID: References: <4EA52E30.4010704@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigA65E34382CDDD5EBFED6FDCD" X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:7.0.1) Gecko/20111004 Thunderbird/7.0.1 In-Reply-To: <4EA52E30.4010704@gmail.com> X-Enigmail-Version: 1.1.2 Subject: Re: Questions about using gvirstor as a RAID0 solution X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2011 10:13:12 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigA65E34382CDDD5EBFED6FDCD Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 24/10/2011 11:21, carlopmart wrote: > Hi all, >=20 > I would like to use gvirstor as a thin provisioning solution for a > mysql server, but I have some doubts about using it: Yes, it's kind of what it was created for... > a) Do I need to put "geom_virstor_load=3DYES"" on loader.conf or this > kernel module is loaded automatically at boot If I create gvirstor > volume using the label option?? You need to load the module yourself, the same as with other GEOM modules= =2E > b) Does gvirstor supports UFS journaling?? For example: >=20 > gjournal label /dev/virstor/mydata > newfs -O 2 -J /dev/virstor/mydata You can do that. It will be very inefficient (i.e. you will only avoid fscks, there will probably be no performance gains at all) but nothing should break. Both virstor and gjournal add their overheads (specifically, they can be seek-intensive in different ways), so you wouldn't want to use either if sustained random IO performance is importa= nt. On the other hand, since you are using 9-stable, you can also use the journaled soft-updates instead of gjournal, for much better efficiency. > c) Can i use growfs utility If I need to expand a virstor volume at > filesystem level?? Not exactly; virstor will immediately create a volume with large virtual size (whatever you specify at the volume creation) ragardless of how many physical devices you have. If you add more physical devices to the virstor later, you do not have to do anything with the file system itself, it will still see the original large virtual size. If you are talking about expanding the virtual volume size, that's not implemented yet (and in that case you would need to use growfs). --------------enigA65E34382CDDD5EBFED6FDCD Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6lOigACgkQldnAQVacBchSCwCgyMhV+1SbKLjsQjBjB2mFpot5 In0Anj3kTUqFKCfKtoLgz4fQ9RKmStXm =oWPK -----END PGP SIGNATURE----- --------------enigA65E34382CDDD5EBFED6FDCD--