From owner-freebsd-fs@FreeBSD.ORG  Mon Feb 23 03:43:44 2009
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 3EF71106564A
	for <freebsd-fs@freebsd.org>; Mon, 23 Feb 2009 03:43:44 +0000 (UTC)
	(envelope-from k0802647@telus.net)
Received: from defout.telus.net (defout.telus.net [199.185.220.240])
	by mx1.freebsd.org (Postfix) with ESMTP id DD43A8FC1A
	for <freebsd-fs@freebsd.org>; Mon, 23 Feb 2009 03:43:43 +0000 (UTC)
	(envelope-from k0802647@telus.net)
Received: from priv-edtnaa06.telusplanet.net ([75.157.11.254])
	by priv-edtnes28.telusplanet.net
	(InterMail vM.7.08.04.00 201-2186-134-20080326) with ESMTP id
	<20090223034343.MDTZ26993.priv-edtnes28.telusplanet.net@priv-edtnaa06.telusplanet.net>;
	Sun, 22 Feb 2009 20:43:43 -0700
Received: from oliver.bc.lan (d75-157-11-254.bchsia.telus.net [75.157.11.254])
	by priv-edtnaa06.telusplanet.net (BorderWare Security Platform) with
	ESMTP id 12702B0230197942; Sun, 22 Feb 2009 20:43:42 -0700 (MST)
Received: from [10.111.111.112] (unknown [10.111.111.112])
	by oliver.bc.lan (Postfix) with ESMTP id 4F9A162AA;
	Sun, 22 Feb 2009 19:43:40 -0800 (PST)
Message-ID: <49A21B6B.7060709@telus.net>
Date: Sun, 22 Feb 2009 19:43:39 -0800
From: Carl <k0802647@telus.net>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: Kevin Day <toasty@dragondata.com>
References: <49A10626.8060705@telus.net>
	<20090222110052.GH41617@deviant.kiev.zoral.com.ua>
	<49A1E5CE.5000501@telus.net>
	<CB040010-5DF9-4E73-9A15-63F01523D2F2@dragondata.com>
In-Reply-To: <CB040010-5DF9-4E73-9A15-63F01523D2F2@dragondata.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-fs@freebsd.org
Subject: Re: UFS2 and/or sparse file bug causing copy process to land in 'D''
 state?
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Feb 2009 03:43:44 -0000

Kevin Day wrote:
> On Feb 22, 2009, at 5:54 PM, Carl wrote:
>> Is there some other way to forcibly reboot a remote system from the 
>> command line when a normal shutdown command is going to totally hang 
>> the system in this way? Or perhaps some kind of watchdog that has a 
>> good chance of surviving long enough to unjam a situation like this?
> 
> reboot(8)'s man page:
> 
>      -n      The file system cache is not flushed.  This option should 
>              probably not be used.
> 
>      -q      The system is halted or restarted quickly and ungracefully, 
>              and only the flushing of the file system cache is
 >              performed (if the -n option is not specified).  This
 >              option should probably not be used.
> 
> One or both of those would probably do it.

Obviously I need to work on RTFM. I didn't look past shutdown(8). In my 
defence... I've got nothing. Thanks Kevin :-)

A watchdog would still be valuable for those situations when one 
attempts a normal remote reboot, the system hangs, and sshd dies with it.

Carl                                             / K0802647