From owner-freebsd-questions@FreeBSD.ORG Tue Jul 28 21:16:17 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 CECD5106568A for ; Tue, 28 Jul 2009 21:16:17 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) by mx1.freebsd.org (Postfix) with ESMTP id 8BD4C8FC5C for ; Tue, 28 Jul 2009 21:16:17 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r55.edvax.de (port-92-195-59-134.dynamic.qsc.de [92.195.59.134]) by mx02.qsc.de (Postfix) with ESMTP id 3649C1E128; Tue, 28 Jul 2009 23:16:15 +0200 (CEST) Received: from r55.edvax.de (localhost [127.0.0.1]) by r55.edvax.de (8.14.2/8.14.2) with SMTP id n6SLGAIH001890; Tue, 28 Jul 2009 23:16:10 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Tue, 28 Jul 2009 23:16:10 +0200 From: Polytropon To: "Edward Sanford Sutton, III" Message-Id: <20090728231610.9d7c9299.freebsd@edvax.de> In-Reply-To: <200907281407.13445.mirror176@cox.net> References: <200907281407.13445.mirror176@cox.net> Organization: EDVAX X-Mailer: Sylpheed 2.4.7 (GTK+ 2.12.1; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: fsck and dump freeze freebsd. any ideas? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jul 2009 21:16:18 -0000 On Tue, 28 Jul 2009 14:07:13 -0700, "Edward Sanford Sutton, III" wrote: > As a final question, is there any safe way to crash freebsd (or pull system > power) without a risk of filesystem corruption? An "easy" way is to go into single user mode and umount all the partitions, then press Reset or Power off. Most cases of file system corruption on hard reset or power loss are often repaired well by the fsck program. (I had system crashes due to defective USB sticks and never had file system corruption after a successful fsck run. Note that I did fsck in the foreground.) If you cannot umount disks, run "sync" three or four times and wait a little while. This is not "as good" as umounting disks, and quite useless if the system is active (in terms of file I/O). -- Polytropon >From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...