From owner-freebsd-stable@FreeBSD.ORG Thu Aug 6 09:54:58 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 2675B1065675 for ; Thu, 6 Aug 2009 09:54:58 +0000 (UTC) (envelope-from cptsalek@gmail.com) Received: from mail-ew0-f206.google.com (mail-ew0-f206.google.com [209.85.219.206]) by mx1.freebsd.org (Postfix) with ESMTP id A77E98FC1E for ; Thu, 6 Aug 2009 09:54:57 +0000 (UTC) Received: by ewy2 with SMTP id 2so733627ewy.43 for ; Thu, 06 Aug 2009 02:54:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=cN3OK95G10pmHLpc40Fd6ONlTS6XXCWtbXkJQrs7n2Q=; b=grbAbopTuqODh0b8EZz7LgK58fbIiJBZ5JKUAlrZjgoCvs8LPbUmqGoiYn5WhCibPE z2d4xFkJUb6HgRtv5g2OKuUEyomGFMJaIrhiw2Mr0gwSauhsY/Ti2txoQnnw+9w5mlVc ShbegD7qNkhIXasexOCtvu11GnG0U5qEollfs= 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:content-transfer-encoding; b=oFUyfaxJkFGdGHkAQjkr/IAbiMS6oE4zNh+cZzT9PDNwdl651KLw7MU6g0ePH4O/r6 Mye+ksLEpKv1+WGhjZZgqW16lxpkrnbKZqrHudDRhE1vyjAqVHgFgs4PcqlscMZ2k/5w doqs7GZYMepXbDx8s/wcQ2GvcqzuQaOJTyKCI= MIME-Version: 1.0 Received: by 10.210.76.6 with SMTP id y6mr77291eba.76.1249552496504; Thu, 06 Aug 2009 02:54:56 -0700 (PDT) In-Reply-To: References: <659cf8870907270259m2e23769dxf416a3c86f9e8c50@mail.gmail.com> Date: Thu, 6 Aug 2009 11:54:56 +0200 Message-ID: <14989d6e0908060254k7c3deceap27d6c4d0c582cef9@mail.gmail.com> From: Christian Walther To: Matthias Andree Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Cristiano Deana , freebsd-stable@freebsd.org 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:55:03 -0000 Hi 2009/8/6 Matthias Andree : > Probably not fsck's fault, but if there is a major file system corruption, > it can wreak havoc. Yes, it can. But on the other hand the question is if one is capable of dealing with a major file system corruption during a manual fsck run. It requires in depth knowledge of the filesystem specification, and what each question really means. The whorst case I've seen so far was a linux ext2 FS that wiped entirely by fsck. Nearly 200GB of data were lost and had to be restored from the last backup. I personally like fsck -y (because I certainly don't have this knowledge) and pray that my FS comes out intact. If it doesn't, well, it's time to do a restore. ;-) Christian