From owner-freebsd-stable@FreeBSD.ORG Thu Jul 14 19:14:51 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2CFA516A41C; Thu, 14 Jul 2005 19:14:51 +0000 (GMT) (envelope-from oberman@es.net) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id F095943D46; Thu, 14 Jul 2005 19:14:50 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP (SSL) id IBA74465; Thu, 14 Jul 2005 12:14:49 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id A8A615D07; Thu, 14 Jul 2005 12:14:49 -0700 (PDT) To: Anatoliy Dmytriyev In-reply-to: Your message of "Thu, 14 Jul 2005 20:38:15 +0200." <42D6B117.5080302@plab.ku.dk> Date: Thu, 14 Jul 2005 12:14:49 -0700 From: "Kevin Oberman" Message-Id: <20050714191449.A8A615D07@ptavv.es.net> Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: dangerous situation with shutdown process 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, 14 Jul 2005 19:14:51 -0000 > Date: Thu, 14 Jul 2005 20:38:15 +0200 > From: Anatoliy Dmytriyev > Sender: owner-freebsd-stable@freebsd.org > > Hello, everybody! > > I have found unusual and dangerous situation with shutdown process: > I did a copy of 200 GB data on the 870 GB partition (softupdates is > enabled) by cp command. > It took a lot of time when I did umount for this partition exactly after > cp, but procedure finished correctly. > In case, if I did “shutdown –h(r)”, also exactly after cp, the shutdown > procedure waited for “sync” (umounting of the file system) but sync > process was terminated by timeout, and fsck checked and did correction > of the file system after boot. > > System 5.4-stable, RAM 4GB, processor P-IV 3GHz. > > How can I fix it on my system? SCSI or ATA? If it's ATA, turn off write cache with (atacontrol(8) or the sysctl. The problem is that disks lie about whether they have actually written data. If the power goes off before the data is in cache, it's lost. I am not sure if write-cache can be turned off on SCSI, but SCSI drives seem less likely to lie about when the data is actually flushed to the drive. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634