From owner-freebsd-stable@FreeBSD.ORG Fri Jul 15 15:08:33 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 646F816A41C for ; Fri, 15 Jul 2005 15:08:33 +0000 (GMT) (envelope-from bv@bilver.wjv.com) Received: from wjv.com (fl-65-40-24-38.sta.sprint-hsd.net [65.40.24.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7833243D45 for ; Fri, 15 Jul 2005 15:08:32 +0000 (GMT) (envelope-from bv@bilver.wjv.com) Received: from bilver.wjv.com (localhost.wjv.com [127.0.0.1]) by wjv.com (8.12.11/8.13.1) with ESMTP id j6FF8Tpm076707 for ; Fri, 15 Jul 2005 11:08:30 -0400 (EDT) (envelope-from bv@bilver.wjv.com) Received: (from bv@localhost) by bilver.wjv.com (8.12.11/8.13.1/Submit) id j6FF8T89076706 for freebsd-stable@freebsd.org; Fri, 15 Jul 2005 11:08:29 -0400 (EDT) (envelope-from bv) Date: Fri, 15 Jul 2005 11:08:29 -0400 From: Bill Vermillion To: freebsd-stable@freebsd.org Message-ID: <20050715150829.GC76303@wjv.com> References: <20050714223127.34EDB16A422@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050714223127.34EDB16A422@hub.freebsd.org> Organization: W.J.Vermillion / Orlando - Winter Park ReplyTo: bv@wjv.com User-Agent: Mutt/1.5.6i X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.0.4 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on bilver.wjv.com Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bv@wjv.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jul 2005 15:08:33 -0000 On Thu, Jul 14, 2005 at 22:31 , freebsd-stable-request@freebsd.org moved his mouse, rebooted for the change to take effect, and then said: > Message: 13 > Date: Thu, 14 Jul 2005 20:38:15 +0200 > From: Anatoliy Dmytriyev > Subject: dangerous situation with shutdown process > To: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org > Message-ID: <42D6B117.5080302@plab.ku.dk> > Content-Type: text/plain; charset=UTF-8; format=flowed > 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? Copying very large files and then shutting down I hope is not a normal procecure for you. softupdates sometimes do take a long time when you are removing/copying very large files. Others have suggested different time-outs but you'd have to figure out the largest size you may every encounter and set things for that, which is not going to help for everyday operation. I've watched the amount of disk space increase slowly by performing 'df' and it can take a long time - up to a minute on some extremely large partitions I was cleaning. One way to force everything to be written I've found [by observation only] is to perform an fsck on that file system. If you only do huge copies and immediate shutdowns rarely, then maybe it's just a good idea to remember how softupdates work, and then fsck, then shutdown. I'm always against changing default operations from typical operations to extremes. Bill -- Bill Vermillion - bv @ wjv . com