From owner-freebsd-questions@FreeBSD.ORG Tue Nov 4 19:02:35 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3AA7310656B3 for ; Tue, 4 Nov 2008 19:02:35 +0000 (UTC) (envelope-from c.kworr@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.185]) by mx1.freebsd.org (Postfix) with ESMTP id B2F298FC17 for ; Tue, 4 Nov 2008 19:02:34 +0000 (UTC) (envelope-from c.kworr@gmail.com) Received: by nf-out-0910.google.com with SMTP id h3so1347189nfh.33 for ; Tue, 04 Nov 2008 11:02:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=UOisUqZ/nU3w8RGzEV9ISWPV2lhwcIvjmrUMwpkkcdc=; b=YVuURdP25Qd0oRXCTp0sv2mtFODKxS5FGQ7OQBvFa66BlmDbfUTUwVaNJ28+D1uMjG qjnqco+oASpsDSgZMOvDEM53EPvnUxVFjSEH7pLEfWZ3n9LFsSRPks6Gt5AVo04aA9VH OphYdWaVpf4jAG9UgeJlxtGDJ5NU4sA/Sk3Wk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=uLBPQMmuxyWgfF+GEgQ1bQUSOYgyFAiqSfiXLV7irShpfD1V75Cvg5zMxlloz2hPEu DCYqM0mBzPJjvSFH8L2pEzI2dQiJ912pidBqkXWAkLZyGF+ONBVrsL2BCXKMzMBaI3Jd /vYLx6BlJ2C5pYogBQq4/g9KXopuAvr3gJ4P8= Received: by 10.210.58.13 with SMTP id g13mr2004013eba.183.1225823708731; Tue, 04 Nov 2008 10:35:08 -0800 (PST) Received: by 10.210.12.4 with HTTP; Tue, 4 Nov 2008 10:35:08 -0800 (PST) Message-ID: <25ae98a90811041035s57f84718tf1ea3c8ffd9c6fa4@mail.gmail.com> Date: Tue, 4 Nov 2008 20:35:08 +0200 From: "Volodymyr Kostyrko" To: "Gabriel Lavoie" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <48FD6665.5000102@telus.net> <48FD6803.7080802@shopzeus.com> <48FE6C64.7060606@telus.net> Cc: freebsd-questions@freebsd.org Subject: Re: gjournal: journaled slices vs. journaled partitions X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2008 19:02:35 -0000 2008/11/4 Gabriel Lavoie : > When building this setup I got one big problem. If the root filesystem (/) > was on a gjournal provider, an unclean shutdown when data was being written > on the disk rendered the system completely unbootable. I got this message: > > GEOM_MIRROR: Device mirror/gm launched (2/2) > GEOM_JOURNAL: Journal 3672855181: mirror/gma contains data. > GEOM_JOURNAL: Journal 3672855181: mirror/gma contains journal. > GEOM_JOURNAL: Journal 3868799910: mirror/gmd contains data. > > GEOM_JOURNAL: Journal 3868799910: mirror/gmd contains journal. > GEOM_JOURNAL: Journal mirror/gmd consistent. Just one thing - you have two separate journaled partitions, one journal per one partition. > Trying to mount root from ufs:/dev/mirror/gm.journal > > Manual root filesystem specification: > : Mount using filesystem > > eg. ufs:da0s1a > ? List valid disk boot devices > Abort manual input > > > mountroot> ? > > List of GEOM managed disk devices: > > mirror/gmd.journal mirror/gmd mirror/gmc mirror/gma mirror/gm ad10s1c > ad10s1b ad8s1c ad8s1b ad10s2 ad10s1 ad8s1 ad10 ad8 acd0 > > As you can see, in the proposed list of disk devices devices to boot on, > "mirror/gm.journala" is absent. As I and Ivan Voras, that I contacted about > this problem, found, the GEOM_JOURNAL thread that is supposed to mark the > journal consistent takes too much time to do it with the root filesystem's > provider and the kernel try to mount a device that doesn't yet exist. A bug > report has been opened about this problem. For my final setup I decided to > put the root filesystem on a separate mirrorred slice of 1GB. Since this > slice isn't often written on, not many rebuilds should occur in case of > power failure. And I made my "power failure" test by hitting the reset > button while writing data on this filesystem and the rebuild on 1GB doesn't > takes too much time (at most 20-30 seconds). Good to hear it, i've fallen for that too, but the machine isn't powercycled at all and runs on guaranteed power. I had the similar problems with described setup on virtual test machine too, yet entering anything at mountroot> prompt gave gjournal a chance to keep up and needed partition comes up eventually... I didn't reported that, thought it was a virtual machine issue. > Now I have the question. Why the "load" algorith wasn't recommended? Is it > fixed in 7.0-RELEASE-p5? Nope... http://www.freebsd.org/cgi/query-pr.cgi?pr=113885 -- Sphinx of black quartz judge my vow.