From owner-freebsd-stable@FreeBSD.ORG Tue May 13 21:17:56 2008 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 75C671065670 for ; Tue, 13 May 2008 21:17:56 +0000 (UTC) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (merlin.alerce.com [64.62.142.94]) by mx1.freebsd.org (Postfix) with ESMTP id 5E8B38FC21 for ; Tue, 13 May 2008 21:17:56 +0000 (UTC) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (localhost [127.0.0.1]) by merlin.alerce.com (Postfix) with ESMTP id F23B633C62; Tue, 13 May 2008 14:17:55 -0700 (PDT) Received: from postfix.alerce.com (w092.z064001164.sjc-ca.dsl.cnc.net [64.1.164.92]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by merlin.alerce.com (Postfix) with ESMTP id BADA833C5B; Tue, 13 May 2008 14:17:55 -0700 (PDT) Received: by postfix.alerce.com (Postfix, from userid 501) id EFDBC42C649; Tue, 13 May 2008 14:17:54 -0700 (PDT) From: George Hartzell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18474.1410.744898.778947@almost.alerce.com> Date: Tue, 13 May 2008 14:17:54 -0700 To: Adam McDougall In-Reply-To: <4829FBC8.5040101@egr.msu.edu> References: <18473.48984.31132.91673@almost.alerce.com> <4829FBC8.5040101@egr.msu.edu> X-Mailer: VM 7.19 under Emacs 22.1.50.1 X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-stable@freebsd.org Subject: Re: good/best practices for gmirror and gjournal on a pair of disks? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hartzell@alerce.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 21:17:56 -0000 Adam McDougall writes: > [...] > I believe gjournal uses 1G for journal (2x512) which seemed to be > sufficient on all of the systems where I have used the default, but I > quickly found that using a smaller journal is a bad idea and leads to > panics that I was unable to avoid with tuning. Considering 1G was such > a close value, I chose to go several times above the default journal > size (disk is cheap and I want to be sure) but I ran into problems using > gjournal label -s (size) rejecting my sizes or wrapping the value around > to something too low. [...] I also stumbled on this and was unable to find any mention of it in the pr database. One of my todo items is to make sure I'm not messing up somehow, dig further into the PR db for an existing report, and file one if I can't find one? I tried -s 2147483648 and it was found to be "too small". A quick read of the source led me to find that jsize is an intmax_t and that gctl_get_intmax() should be returning an intmax_t and that intmax_ ought to be an __int64_t (I'm on amd64), which left me confused. Has anyone else seen/reported a problem with gjournal -s and values > 1G? g.