From owner-freebsd-geom@FreeBSD.ORG Fri Jan 16 07:47:47 2009 Return-Path: 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 9277A1065670 for ; Fri, 16 Jan 2009 07:47:47 +0000 (UTC) (envelope-from lev@serebryakov.spb.ru) Received: from ftp.translate.ru (ftp.translate.ru [195.131.4.140]) by mx1.freebsd.org (Postfix) with ESMTP id 47CF68FC12 for ; Fri, 16 Jan 2009 07:47:47 +0000 (UTC) (envelope-from lev@serebryakov.spb.ru) Received: from desktop.home.serebryakov.spb.ru (blacklion.dialup.corbina.ru [89.179.122.169]) (Authenticated sender: lev@serebryakov.spb.ru) by ftp.translate.ru (Postfix) with ESMTPA id 9063913DF60; Fri, 16 Jan 2009 10:43:43 +0300 (MSK) Date: Fri, 16 Jan 2009 10:32:29 +0300 From: Lev Serebryakov X-Priority: 3 (Normal) Message-ID: <529173009.20090116103229@serebryakov.spb.ru> To: "Rick C. Petty" In-Reply-To: <20090115172036.GA54383@keira.kiwi-computer.com> References: <2b5f066d0901141323j7c9a194eo4606d9769279037e@mail.gmail.com> <20090115025645.21ad2185.ota@j.email.ne.jp> <2b5f066d0901150410s7dc4e97v741d5edd2a4983a9@mail.gmail.com> <20090115172036.GA54383@keira.kiwi-computer.com> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: Brian McCann , freebsd-geom@freebsd.org Subject: Re[2]: gvinum & gjournal X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jan 2009 07:47:47 -0000 Hello, Rick. You wrote 15 =FF=ED=E2=E0=F0=FF 2009 =E3., 20:20:36: > You don't *have* to fsck with UFS2 either, if you're using soft updates. > The only thing fsck does is free up space and inodes that are marked as > used but are really not used. Since it can be done successfully in the > background, I don't see much of a problem (yes it will take hours, so > schedule the checks at times when you have the least I/O traffic). background fsck on 2Tb (RAID-5 on 5x500Gb drives) in same time as raid5 rebuilding (due to same reasons as fsck: dirty reboot) is pain in ass, really. It finishes never. I was need to stop RAID5 rebuilding, umount filesystem, run fsck by hands (with lots of questions about strange softupdate inconsistences) TWICE and rebuild RAID5 after that. Only thing I lost is 6 or 7 files which were "in flight" at time of crash. So, yes, it is safe for information (nobody expect to have files in flight to be safe in case of crash, of course) but it does not work automagically after reboot... I'm thinking about gjournal, but it KILLS performance in case of fast RAID array without additional super-fast (SSD?) place for journal :( --=20 // Black Lion AKA Lev Serebryakov