From owner-freebsd-stable@FreeBSD.ORG  Thu Jul 14 18:38:17 2005
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
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 C083716A41C;
	Thu, 14 Jul 2005 18:38:17 +0000 (GMT)
	(envelope-from tolid@plab.ku.dk)
Received: from plab.ku.dk (plab.ku.dk [130.225.107.20])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 501AB43D46;
	Thu, 14 Jul 2005 18:38:17 +0000 (GMT)
	(envelope-from tolid@plab.ku.dk)
Received: from plab.ku.dk (localhost [127.0.0.1])
	by plab.ku.dk (Postfix) with SMTP id 6C8A2562421;
	Thu, 14 Jul 2005 20:38:16 +0200 (CEST)
Received: from [192.168.1.2] (david.tolid.eu.org [213.237.119.114])
	by plab.ku.dk (Postfix) with ESMTP id 0A09D562420;
	Thu, 14 Jul 2005 20:38:15 +0200 (CEST)
Message-ID: <42D6B117.5080302@plab.ku.dk>
Date: Thu, 14 Jul 2005 20:38:15 +0200
From: Anatoliy Dmytriyev <tolid@plab.ku.dk>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: 
Subject: 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 <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jul 2005 18:38:17 -0000

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?


-- 
Anatoliy Dmytriyev
<tolid@plab.ku.dk>