From owner-freebsd-stable@FreeBSD.ORG Sun Jun 24 16:34:45 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 969D9106564A for ; Sun, 24 Jun 2012 16:34:45 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 248DF8FC08 for ; Sun, 24 Jun 2012 16:34:44 +0000 (UTC) Received: by wgbds11 with SMTP id ds11so3169425wgb.31 for ; Sun, 24 Jun 2012 09:34:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=hID/R69aRPQf3msSXY3jwl2Xl77FU3vxYA0fAHo8VcU=; b=lP5Hp9X89gPXchb0W7rwciY4fQ1ozA1SwAx12VCkT1cq9aTNz2y2id0F4e8ap+o7AJ fJRRlbQwesyDSsiCa9+BF/eWEbavo5cSfOT0IBWJENiXTdTN2cUNTsDAoFXz6sxp6CRv aowUt123WYVf0RFyegAd52+oeKNVGBMe5e5eqIGuCtWCdHztA7TcInfc64W2nOjMp7S+ wy7haQrll4EMJ4p2+TE1wd5h3f4POvhZUC9B5+pE2NvrqIajiw5m8lddypn8dH+uay/5 UBr1DUA6ZNfJwJvRUWC/f2HysQJ/66Cifg4bz7MjIYZGYbaM1+R18PvvXmExkQyzsPFN 8ahw== MIME-Version: 1.0 Received: by 10.216.145.13 with SMTP id o13mr4427164wej.95.1340555684041; Sun, 24 Jun 2012 09:34:44 -0700 (PDT) Received: by 10.223.155.4 with HTTP; Sun, 24 Jun 2012 09:34:43 -0700 (PDT) In-Reply-To: <20120624160631.GA80121@DataIX.net> References: <1340401637.32116.YahooMailNeo@web113519.mail.gq1.yahoo.com> <3729A720-2C8F-4C84-B05A-201394C40D63@gothic.net.au> <20120624013624.GG24842@portland1.byshenk.net> <20120624025451.GA17721@DataIX.net> <20120624160631.GA80121@DataIX.net> Date: Sun, 24 Jun 2012 09:34:43 -0700 Message-ID: From: Kevin Oberman To: "J. Hellenthal" Content-Type: text/plain; charset=UTF-8 Cc: Adam Vande More , Greg Byshenk , "freebsd-stable@freebsd.org" , "Leonardo M. Ram?" Subject: Re: fsck_ufs running too often X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jun 2012 16:34:45 -0000 On Sun, Jun 24, 2012 at 9:06 AM, J. Hellenthal wrote: > > > On Sat, Jun 23, 2012 at 10:15:19PM -0500, Adam Vande More wrote: >> On Sat, Jun 23, 2012 at 9:54 PM, Jason Hellenthal wrote: >> > >> > At one point it was proven that background fsck was not benefitial. >> >> >> Where can we find this "proof"? >> > > It was in the lists amongst many conversations. I think the term 'proof' is being abused here. Proof is rigorous, demonstrable and precise. It is not a non-specific coalescence of bit and pieces in a mail thread. My experience with background fsck is that its benefit is entirely dependent on the requirements of the system. A few things are entirely clear and easily demonstrated. (Note, this is an assertion and not proof.) 1. Background fsck takes considerably longer to run than fsck 2. fsck places a very substantial I/O load on the system, primarily on the disk undergoing the check 3. Other system activity that requires I/O to the disk being checked will slow 4. Background fsck is limited and, when it cannot correct some problems can impact system stability, especially in the event of power failure 5. For systems with large file systems it will make the system available for use MUCH sooner than would be the case if a standard fsck was used As with almost all system performance issues, background fsck requires looking at its benefits and costs. For some, it is a big win. For others it is a losing proposition because a server is rendered effectively useless for an extended period. Full disclosure: I have disabled background fsck on most of the systems for which I am responsible, but not all. -- R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com