From owner-freebsd-current@FreeBSD.ORG Thu Sep 1 11:04:49 2011 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 83B2E1065670 for ; Thu, 1 Sep 2011 11:04:49 +0000 (UTC) (envelope-from niclas.zeising@gmail.com) Received: from mail.lysator.liu.se (mail.lysator.liu.se [IPv6:2001:6b0:17:f0a0::3]) by mx1.freebsd.org (Postfix) with ESMTP id DF8AC8FC18 for ; Thu, 1 Sep 2011 11:04:48 +0000 (UTC) Received: from mail.lysator.liu.se (localhost [127.0.0.1]) by mail.lysator.liu.se (Postfix) with ESMTP id 9929E4001D for ; Thu, 1 Sep 2011 13:04:47 +0200 (CEST) Received: by mail.lysator.liu.se (Postfix, from userid 1004) id 8AFE440013; Thu, 1 Sep 2011 13:04:47 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on bernadotte.lysator.liu.se X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=AWL,FREEMAIL_FROM autolearn=disabled version=3.3.1 X-Spam-Score: 0.0 Received: from mx.daemonic.se (mx.daemonic.se [IPv6:2001:470:dca9:0:1::3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.lysator.liu.se (Postfix) with ESMTPSA id A941040018; Thu, 1 Sep 2011 13:01:34 +0200 (CEST) Received: from mail.daemonic.se (mail.daemonic.se [IPv6:2001:470:dca9:0:1::4]) by mx.daemonic.se (Postfix) with ESMTPS id D6A1E119C04; Thu, 1 Sep 2011 13:00:39 +0200 (CEST) Received: from [IPv6:2001:470:dca9:1::4] (vivi.daemonic.se [IPv6:2001:470:dca9:1::4]) by mail.daemonic.se (Postfix) with ESMTPSA id 7D3FA12B0A0; Thu, 1 Sep 2011 13:00:39 +0200 (CEST) Message-ID: <4E5F65CC.1090200@gmail.com> Date: Thu, 01 Sep 2011 13:00:28 +0200 From: Niclas Zeising User-Agent: Mutt/1.5.21 MIME-Version: 1.0 To: "Hartmann, O." References: <4E5E70AF.2080806@zedat.fu-berlin.de> <4E5E773E.4050806@zedat.fu-berlin.de> In-Reply-To: <4E5E773E.4050806@zedat.fu-berlin.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: Garrett Cooper , freebsd-current Subject: Re: howto: enabling journaling on softupdates 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: Thu, 01 Sep 2011 11:04:49 -0000 On 2011-08-31 20:02, Hartmann, O. wrote: > On 08/31/11 19:56, Garrett Cooper wrote: >> On Wed, Aug 31, 2011 at 10:34 AM, Hartmann, O. >> wrote: >>> I try to find a suitable reading/howto for how to enable softupdates >>> on >>> UFS2 filesystems. >> Agreed. Added to http://wiki.freebsd.org/DocsFor9x . > Many thanks. > >>> As I could see, SU+J is enlisted to be enabled by default in >>> 9.0-RELEASE. >> Yes, it is on by default in bsdinstall (and I think in newfs? I could >> be wrong). > Great! > >>> What is the status quo of that? I've several active systems running >>> UFS2 on their system disks while data/home/mass storage is ZFS. >>> Are their any issue with SU+J? >> I haven't been tracking what's been going on, but several bugfixes >> have gone in in the last couple of months post-SUJ. There might be >> some bugs in the work, but most standard operations work out of the >> box for me at least. >> >> ... >> >>> I hit was "-J", the option for enabling softupdate via GEOM gjournal. >> Yeah, it's confusing.. >> >>> Is there any special preparation to bring up an existing filesystem >>> securely into >>> journaling? As I read the blogs and emails in the list, it should be >>> as simple >>> as booting into single user mode, enabling on all partitions in >>> question (even / ?) >> Yes. >> >>> via -j softupdate-journaling, runing a foreground fsck, reboot ... >>> that's it? >> If all goes well, that was the entire process IIRC. > > To late ... ;-) I couldn't resist the temptation, shut down the box, > reboot single user mode, > enabled "-j" (the lower letter `j' !!!), did a full fsck -y ... rebooted > ... >>> Or is there any other additional preparation like mentioned in >>> gjournal >>> (async mount)? >> ENOCLUE (because I'm not aware of that with gjournal -- the last time >> I tried setting it up things didn't work too well for me) :). >> >>> Thanks for patience and repsonding, >> Sure :)! >> -Garrett >> _____________ > > ... and here I am again with SU+J on my box ;-) > > Tomorrow, I will perform this step on all servers. I guess it's a "worth > having". > > > Oliver Can you please detail a little more the steps you took to enable SU+J and your experience with it? It sounds like a good start for a howto or an inclusion in the handbook. Thanks! -- Niclas Zeising