From owner-freebsd-questions@FreeBSD.ORG Sun Apr 5 20:40:53 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E3D31065676 for ; Sun, 5 Apr 2009 20:40:53 +0000 (UTC) (envelope-from utisoft@googlemail.com) Received: from mail-ew0-f171.google.com (mail-ew0-f171.google.com [209.85.219.171]) by mx1.freebsd.org (Postfix) with ESMTP id F01DA8FC12 for ; Sun, 5 Apr 2009 20:40:52 +0000 (UTC) (envelope-from utisoft@googlemail.com) Received: by ewy19 with SMTP id 19so1581149ewy.43 for ; Sun, 05 Apr 2009 13:40:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=/SsWm7Hvjg/2SqmL3dxAihJmHlU+pIqOo8N5mRWmPX8=; b=bVbUGfZj8qr7bHeUVga1goLVn7MTBxxmcV6PYuujeLINLiSVH6zILNHCnLF41whJUJ ucu69y0ionf8+xIKA/FQRYj0dYotlDDZRT7Wh2+6C0Cyffuv7aAlYiS4b+LtBUdrVglm 6xf64EKCit0+ljrO6K/fVAD326f80tIhtvBL0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:content-type:content-transfer-encoding; b=n2ftfgr5+ld6bXqJQ5UEZaEIxZstjwSUXnJWglOTPw2/iPeg9OfQ7anZZhVmsFwMup CPImbNfgpecSkagIFVYrLOp2DJHpFhxm1o97GRzzTOjTW/eM06VhnueXm+/NjkmvWovi 1lew4Wude0WCynexmRy1H8SWmtgjfnLwVgXnc= MIME-Version: 1.0 Received: by 10.210.18.8 with SMTP id 8mr2762682ebr.27.1238964052102; Sun, 05 Apr 2009 13:40:52 -0700 (PDT) In-Reply-To: <200903311657.n2VGvLE8010101@lurza.secnetix.de> References: <200903311657.n2VGvLE8010101@lurza.secnetix.de> Date: Sun, 5 Apr 2009 21:40:52 +0100 Message-ID: From: Chris Rees To: freebsd-questions@freebsd.org, Wojciech Puchar , olli@lurza.secnetix.de, ertr1013@student.uu.se Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Subject: Re: Question about forcing fsck at boottime X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: utisoft@gmail.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Apr 2009 20:40:54 -0000 2009/3/31 Oliver Fromme : > Chris Rees wrote: > =A0> 2009/3/31 Wojciech Puchar : > =A0> > > =A0> > IMHO this background fsck isn't good idea at all > =A0> > =A0> Why? > > Google "background fsck damage". > > I was bitten by it myself, and I also recommend to turn > background fsck off. =A0If your disks are large and you > can't afford the fsck time, consider using ZFS, which > has a lot of benefits besides not requiring fsck. > > Best regards > =A0 Oliver > Right... You were bitten by background fsck, what _exactly_ happened? All the 'problems' here associated with bgfsck are referring to FreeBSD 4 etc, or incredibly vague anecdotal evidence. Have you googled for background fsck damage? Nothing (in the first two pages at least) even suggests that background fsck causes damage. Erik Trulsson wrote: > Normal PATA/SATA disks with write caching enabled (which is the default) = do > not provide these guarantees. Disabling write caching on will make them > adhere to the assumptions that soft updates make, but at the cost of a > severe performance penalty when writing to the disks. > In short therefore on a 'typical' PC you can fairly easily get errors on = a > filesystem which background fsck cannot handle. What do you mean by handle? Sure, it won't fix them, but it'll at least detect them. The chances of actually having a problem are slim, anyway, and it won't cause any damage either. Please don't assert information or stories about being 'bitten', without being more specific. It's meaningless and frustrating; I didn't ask who was bitten, I asked what the problem was. Also, please don't tell me to search the Internet without checking the search results for relevance yourself. I've spent a long time researching this, as have the FreeBSD devs, and they chose to make it on by default with no warnings. From the petty things they DO warn about, I very much doubt they'd allow something with a chance of any data corruption slide like that. Concrete evidence or direct links to problems with FreeBSD >6.0 ONLY in response please. Or, no-one has proven any reason for distrust, and all you lot are spreading is FUD. Sorry for the rant, it's not directly aimed at any of you, just the general assertion of 'facts' with no evidence, Chris --=20 A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?