From owner-freebsd-stable@FreeBSD.ORG Thu Aug 6 09:31:53 2009 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 C409C106564A for ; Thu, 6 Aug 2009 09:31:53 +0000 (UTC) (envelope-from ma@dt.e-technik.tu-dortmund.de) Received: from unimail.uni-dortmund.de (mx1.HRZ.Uni-Dortmund.DE [129.217.128.51]) by mx1.freebsd.org (Postfix) with ESMTP id 5491E8FC25 for ; Thu, 6 Aug 2009 09:31:52 +0000 (UTC) Received: from merlin.emma.line.org (g230090238.adsl.alicedsl.de [92.230.90.238]) (authenticated bits=0) by unimail.uni-dortmund.de (8.14.3/8.14.3) with ESMTP id n769BtdK009864 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 6 Aug 2009 11:12:01 +0200 (CEST) Date: Thu, 06 Aug 2009 11:11:55 +0200 To: "Cristiano Deana" , freebsd-stable@freebsd.org From: "Matthias Andree" Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8 MIME-Version: 1.0 References: <659cf8870907270259m2e23769dxf416a3c86f9e8c50@mail.gmail.com> Content-Transfer-Encoding: 7bit Organization: Message-ID: In-Reply-To: User-Agent: Opera Mail/9.64 (Linux) Cc: Subject: Re: Turn off rebooting in single-user mode after fail. 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: Thu, 06 Aug 2009 09:31:54 -0000 Am 27.07.2009, 12:55 Uhr, schrieb Cristiano Deana : > On Mon, Jul 27, 2009 at 11:59 AM, Paul P. wrote: >> Hello. >> How to turn off automatic reboot in single user mode after power fails >> or >> sudden reset? Do i need to make passin value in fstab equal to zero >> just to >> turn off automatic FSCK fs check? > > if i understood correctly: > > rc.conf: > fsck_y_enable="YES" # Set to YES to do fsck -y if the initial preen > fails. This sort of disposed of 8 out of 13 GB on one of my systems after a growfs failure, and after a >24 hrs fsck run... I guess that rsync before fsck could have recovered quite a lot of such data (I can't tell, as I didn't have full image backups). Probably not fsck's fault, but if there is a major file system corruption, it can wreak havoc. -- Matthias Andree