From owner-freebsd-current@FreeBSD.ORG Sun Jan 6 16:10:46 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 54DC616A419; Sun, 6 Jan 2008 16:10:46 +0000 (UTC) (envelope-from srw@udor.net) Received: from mail.udor.net (mail.udor.net [64.34.95.190]) by mx1.freebsd.org (Postfix) with ESMTP id 35E2713C43E; Sun, 6 Jan 2008 16:10:46 +0000 (UTC) (envelope-from srw@udor.net) Received: from localhost (KD121110020099.ppp-bb.dion.ne.jp [121.110.20.99]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.udor.net (Postfix) with ESMTP id 31FF64294; Sun, 6 Jan 2008 11:06:54 -0500 (EST) Date: Mon, 7 Jan 2008 01:10:39 +0900 From: srwadleigh To: Pawel Jakub Dawidek Message-ID: <20080107011039.6f886630@udor.net> In-Reply-To: <20080105150355.GB6472@garage.freebsd.pl> References: <20080102114327.62f661f5@udor.net> <20080105150355.GB6472@garage.freebsd.pl> X-Mailer: Claws Mail 3.0.2 (GTK+ 2.12.3; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/BRHvKKQAf7wU7xIU8wwNOMg"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: freebsd-current@freebsd.org Subject: Re: Gjournal troubles X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jan 2008 16:10:46 -0000 --Sig_/BRHvKKQAf7wU7xIU8wwNOMg Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sat, 5 Jan 2008 16:03:55 +0100 Pawel Jakub Dawidek wrote: > On Wed, Jan 02, 2008 at 11:43:27AM +0900, srwadleigh wrote: > > I am having a strange problem with gjournal on a thinkpad T41, > >=20 > > I am running: 7.0-PRERELEASE - Wed Jan 2 06:05:20 JST 2008 > > And have the problem with both a custom and generic kernel. > >=20 > > If I load gjournal through loader.conf or compile GEOM_JOURNAL into > > the kernel, upon reboot all my slices change, and break booting. > >=20 > > ad0s1a becomes ad0a > > ad0s1d becomes ad0d, and so on.. > >=20 > > If I manually run gjournal load after boot the slices are fine, > > everything works as expected. > >=20 > > Here is my journal setup: > >=20 > > /dev/ad0s1f.journal 64G /usr/home > >=20 > > Geom name: gjournal 2080874044 > > ID: 2080874044 > > Providers: > > 1. Name: ad0s1f.journal > > Mediasize: 70812433920 (66G) > > Sectorsize: 512 > > Mode: r1w1e1 > > Consumers: > > 1. Name: ad0s1f > > Mediasize: 71886176256 (67G) > > Sectorsize: 512 > > Mode: r1w1e1 > > Jend: 71886175744 > > Jstart: 70812433920 > > Role: Data,Journal > >=20 > >=20 > > Doing some research on the list I found a similar problem in the > > past with gmirror, where the slice and device ending at the same > > place was being confused. The solution suggested there seemed to be > > to hardcode the provider names into the metadata. > >=20 > > http://lists.freebsd.org/pipermail/freebsd-stable/2005-May/014448.html > >=20 > > My question is, is this possibly the same issue now with gjournal? > > and is it possible to hardcode provider names after a journal has > > been created? >=20 > Just unmount the file system, stop the journal and call 'gjournal > label' with exactly the sam parameters as originally plus '-h' option. >=20 I will try this, currently my journal is on the same slice as data so I get the used by file system message. I may have to re-configure with a dedicated journal slice so I can use the -f option? Thanks for the help! I will see how it goes. srw --Sig_/BRHvKKQAf7wU7xIU8wwNOMg Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFHgP1/pXXBX0jZoJYRAlx/AKCsOaty/nE/GG4V1bY6pqwEHu04FgCgmg/Z C3dGhUxRNu7eno87h9YVn+g= =Tm54 -----END PGP SIGNATURE----- --Sig_/BRHvKKQAf7wU7xIU8wwNOMg--