From owner-freebsd-geom@FreeBSD.ORG  Wed Mar 17 18:49:27 2010
Return-Path: <owner-freebsd-geom@FreeBSD.ORG>
Delivered-To: freebsd-geom@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 4FDCE1065677;
	Wed, 17 Mar 2010 18:49:27 +0000 (UTC)
	(envelope-from freebsd@chillt.de)
Received: from dd15624.kasserver.com (dd15624.kasserver.com [85.13.136.215])
	by mx1.freebsd.org (Postfix) with ESMTP id 12EA28FC21;
	Wed, 17 Mar 2010 18:49:25 +0000 (UTC)
Received: from taiko.lan (84-203-79-36.mysmart.ie [84.203.79.36])
	by dd15624.kasserver.com (Postfix) with ESMTP id 8A1062C11E5F1;
	Wed, 17 Mar 2010 19:49:24 +0100 (CET)
Message-ID: <4BA12418.3060008@chillt.de>
Date: Wed, 17 Mar 2010 18:48:56 +0000
From: Bartosz Fabianowski <freebsd@chillt.de>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US;
	rv:1.9.1.8) Gecko/20100303 Thunderbird/3.0.3
MIME-Version: 1.0
To: Pawel Jakub Dawidek <pjd@FreeBSD.org>
References: <4B80CEE3.80909@fabianowski.eu>
	<20100221082508.GL1617@garage.freebsd.pl>
In-Reply-To: <20100221082508.GL1617@garage.freebsd.pl>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-geom@freebsd.org
Subject: Re: gjournal failing to do its job
X-BeenThere: freebsd-geom@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: GEOM-specific discussions and implementations
	<freebsd-geom.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-geom>,
	<mailto:freebsd-geom-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-geom>
List-Post: <mailto:freebsd-geom@freebsd.org>
List-Help: <mailto:freebsd-geom-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-geom>,
	<mailto:freebsd-geom-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Mar 2010 18:49:27 -0000

> File system should be placed directly on .journal provider.

I have recreated all file systems, each on its own journal provider. And 
gjournal *still* fails to do it job:

On a normal boot, all journal providers come up as "clean". If the 
system hangs and has to be force-rebooted, the journal providers report 
"consistent" during boot. However, the system still complains that / has 
not been unmounted cleanly. While it only complains about /, all other 
file systems are actually not clean either.

I can return to a consistent state by running fsck on each file system 
and fixing the (numerous) errors it reports. But this surely cannot be 
how journaling is supposed to work...

Am I doing something wrong here? I cannot see what. Each file system is 
UFS2, created directly on its own gjournal provider and with journaling 
flag set.

- Bartosz