From owner-freebsd-stable@FreeBSD.ORG Sun Apr 3 14:29:23 2011 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 6A2D11065674 for ; Sun, 3 Apr 2011 14:29:23 +0000 (UTC) (envelope-from gkontos.mail@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 30C778FC08 for ; Sun, 3 Apr 2011 14:29:22 +0000 (UTC) Received: by iwn33 with SMTP id 33so6229820iwn.13 for ; Sun, 03 Apr 2011 07:29:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=jkeWS86+WRSuIHg0crDlEdAR0cJUaAKl7iP12FLBOww=; b=j0xHkETkS4fXVtO/iEflLOBCfY3iE0lx3aKZZIFbNML6PMQ+7OcrDJOiNJ/gZnPX4y Akcr5jPgO8d7d9k713uXz8xrymxdXaRy8gP/jINzNQWzQug1Q5ulNFlW1aXpjVRv7CbX mQ5mCC7cpnPMv/LjoqNM2iwSO6TwhY91qsO8o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=P06i8L+8UVNSZ2nyPSIAwh9NqH+g0E3QY1QpO6gI4o1Lvc6ojuMsIpaGtoQ5BWOM/I 0nsBZijL0tO86ej524GF2qj3JgX2eZilAC13bUHK5tYXJZOwTn36GDdYqBEleBmwh8fi DjMgMxgc7vAY2DPupb1GGCmw+8fYIi/InawzU= MIME-Version: 1.0 Received: by 10.231.4.139 with SMTP id 11mr6357096ibr.65.1301840962358; Sun, 03 Apr 2011 07:29:22 -0700 (PDT) Received: by 10.231.33.1 with HTTP; Sun, 3 Apr 2011 07:29:22 -0700 (PDT) In-Reply-To: <4D986266.9060205@cran.org.uk> References: <87d3l6p5xv.fsf@cosmos.claresco.hr> <20110401154732.GC37730@ice.42.org> <4D986266.9060205@cran.org.uk> Date: Sun, 3 Apr 2011 17:29:22 +0300 Message-ID: From: George Kontostanos To: Bruce Cran Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Stefan `Sec` Zehl , freebsd-stable@freebsd.org, Marko Lerota Subject: Re: Constant rebooting after power loss 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, 03 Apr 2011 14:29:23 -0000 Those are workarounds. A system should not reach to a point where it doesn't come up because of a pending fsck. And even if it does console access must be ensured. My point is that by disabling these you might bring it up but you seriously risk data integrity. Regards On Sun, Apr 3, 2011 at 3:04 PM, Bruce Cran wrote: > On 01/04/2011 16:47, Stefan `Sec` Zehl wrote: > > If you want to get rid of the reboot loop, set: >> >> background_fsck="NO" >> >> Then it will either come up, or ask for help if anything fails. >> > > I realise that people like having systems that come up quickly after a > crash, but is it worth reconsidering disabling background fsck by default > since it can cause issues like this? > > -- > Bruce Cran > > -- George Kontostanos aisecure.net