Date: Sun, 22 Feb 2009 19:16:52 -0600 From: Kevin Day <toasty@dragondata.com> To: Carl <k0802647@telus.net> Cc: freebsd-fs@freebsd.org Subject: Re: UFS2 and/or sparse file bug causing copy process to land in 'D'' state? Message-ID: <CB040010-5DF9-4E73-9A15-63F01523D2F2@dragondata.com> In-Reply-To: <49A1E5CE.5000501@telus.net> References: <49A10626.8060705@telus.net> <20090222110052.GH41617@deviant.kiev.zoral.com.ua> <49A1E5CE.5000501@telus.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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 proba-
bly 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.
-- Kevin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CB040010-5DF9-4E73-9A15-63F01523D2F2>