From owner-freebsd-amd64@FreeBSD.ORG Sat Nov 1 21:00:12 2008 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 377251065673 for ; Sat, 1 Nov 2008 21:00:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1646A8FC16 for ; Sat, 1 Nov 2008 21:00:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mA1L0Bvc022144 for ; Sat, 1 Nov 2008 21:00:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mA1L0BLc022143; Sat, 1 Nov 2008 21:00:11 GMT (envelope-from gnats) Resent-Date: Sat, 1 Nov 2008 21:00:11 GMT Resent-Message-Id: <200811012100.mA1L0BLc022143@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Joe Kelsey Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5D0C01065670 for ; Sat, 1 Nov 2008 20:57:22 +0000 (UTC) (envelope-from joe@zircon.seattle.wa.us) Received: from dsl254-019-221.sea1.dsl.speakeasy.net (dsl254-019-221.sea1.dsl.speakeasy.net [216.254.19.221]) by mx1.freebsd.org (Postfix) with ESMTP id 0FB398FC1C for ; Sat, 1 Nov 2008 20:57:21 +0000 (UTC) (envelope-from joe@zircon.seattle.wa.us) Received: (qmail 2159 invoked by uid 1001); 1 Nov 2008 20:57:21 -0000 Message-Id: <20081101205721.2158.qmail@zircon.seattle.wa.us> Date: 1 Nov 2008 20:57:21 -0000 From: Joe Kelsey To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 X-Mailman-Approved-At: Sat, 01 Nov 2008 22:42:07 +0000 Cc: Subject: amd64/128524: No geom documentation for loading gjournal X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Joe Kelsey List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Nov 2008 21:00:12 -0000 >Number: 128524 >Category: amd64 >Synopsis: No geom documentation for loading gjournal >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Sat Nov 01 21:00:11 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Joe Kelsey >Release: FreeBSD 7.1-PRERELEASE amd64 >Organization: Joseph M. Kelsey >Environment: System: FreeBSD zircon.zircon.seattle.wa.us 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #26: Mon Oct 27 20:08:55 PDT 2008 root@zircon.zircon.seattle.wa.us:/usr/obj/usr/src/sys/ZIRCON amd64 >Description: I am trying to use gjournal on two different disk drives and have been frustrated over the lack of documentation. To start with, there is no explanation over why certain commands are necessary. For instance, what does the "gjournal load" command do? The man page says that the geom command documents it. However, none of the actual "load" commands are necessary in the standard 7.x kernel build, since everything is loaded by default. However, for some unknowable reason, you actually have to issue the gjournal load command in order to actually cause the various .journal devices to magically appear. This is especially true at boot time. This is in spite of the fact that geom_journal_load is not documented anywhere, relying on someone just guessing that it will cause the right thing to happen. Why do I need to do this? How does this whole thing interact with labels? Why do I sometimes get label devices with, for example, labels1a.journal and sometimes label? What sequence of events causes the label to move from /dev/label/ufs to /dev/ufs to other palces? How to I actually control it? Another problem occurs when you want to experiment with journalling. As soon as you get one method of journalling started, you can never change it because the journal stuff will never let go. For instance, I wanted to reformat my disk to try different ways of setting up partitions on the drive to effectively support journalling. What are the recommended sizes to use for the data versus journal provider? Should I do a newfs on both? I have setteled on 10% for journal and the rest for data with no actual file system on the journal provider. However it took a long time to repartition the disk drive since the stupid journal would not let go of the drive. I had to boot into single user without loading the journal stuff in order to actually have disklabel -e work correctly. There needs to be a reliable way to cause the journalling to let go of the device in order to actually accomplish something. >How-To-Repeat: Run gjournal without doing gjournal load. Look at the various things that do not happen correctly. >Fix: The latest handbook on my disk is different from the handbook on freebsd.org. Why is that? >Release-Note: >Audit-Trail: >Unformatted: