From owner-freebsd-questions@FreeBSD.ORG  Thu Jul 14 20:16:40 2005
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
X-Original-To: freebsd-questions@freebsd.org
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 9A85816A41C;
	Thu, 14 Jul 2005 20:16:40 +0000 (GMT) (envelope-from asym@rfnj.org)
Received: from mail.rfnj.org (ns1.rfnj.org [66.180.172.156])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 50FDF43D48;
	Thu, 14 Jul 2005 20:16:40 +0000 (GMT) (envelope-from asym@rfnj.org)
Received: by mail.rfnj.org (Postfix, from userid 65534)
	id 113A319D; Thu, 14 Jul 2005 16:16:27 -0400 (EDT)
Received: from megalomaniac.rfnj.org (ool-45736df1.dyn.optonline.net
	[69.115.109.241]) by mail.rfnj.org (Postfix) with ESMTP id CCD8738;
	Thu, 14 Jul 2005 16:16:22 -0400 (EDT)
Message-Id: <6.2.1.2.2.20050714161537.0378c310@mail.rfnj.org>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2
Date: Thu, 14 Jul 2005 16:17:06 -0400
To: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org
From: asym <bsdlists@rfnj.org>
In-Reply-To: <20050714191942.GA98637@freebie.xs4all.nl>
References: <42D6B117.5080302@plab.ku.dk>
	<20050714191449.A8A615D07@ptavv.es.net>
	<20050714191942.GA98637@freebie.xs4all.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on rfnj.org
X-Spam-Level: 
X-Spam-Status: No, score=0.0 required=20.0 tests=none autolearn=failed 
	version=3.0.4
Cc: 
Subject: Re: dangerous situation with shutdown process
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jul 2005 20:16:40 -0000

At 15:19 7/14/2005, Wilko Bulte wrote:
>On Thu, Jul 14, 2005 at 12:14:49PM -0700, Kevin Oberman wrote..
> > > Date: Thu, 14 Jul 2005 20:38:15 +0200
> > > From: Anatoliy Dmytriyev <tolid@plab.ku.dk>
> > > 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 =E2=80=9Cshutdown =E2=80=93h(r)=E2=80=9D, also=
 exactly after cp, the=20
> shutdown
> > > procedure waited for =E2=80=9Csync=E2=80=9D (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?

The funny thing about all the replies here.. is that this guy is not saying=
=20
that sync doesn't work.

He's saying that the timeout built into shutdown causes it to *terminate*=20
the sync forcibly before it's done, and then reboot.

All finger pointing about IDE, SCSI, softupdates, and journals aside.. I=20
think all he wants/needs is a way to increase that timer.