Date: Thu, 1 Mar 2007 17:44:42 +1100 From: Peter Jeremy <peterjeremy@optushome.com.au> To: "Daniel O'Connor" <doconnor@gsoft.com.au> Cc: freebsd-stable@freebsd.org Subject: Re: fork wedging (I think) Message-ID: <20070301064442.GG837@turion.vk2pj.dyndns.org> In-Reply-To: <200703011149.02601.doconnor@gsoft.com.au>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On 2007-Mar-01 11:48:54 +1030, Daniel O'Connor <doconnor@gsoft.com.au> wrote: >The problem seems to occur when the acquisition process (called the Recorder) >tries to fork off a new child. Your description and the ps output suggest a filesystem deadlock. >Does anyone have any suggestions for debugging it? I will try and get a crash >dump the next time it happens although it's going to be difficult if I can't >use sysctl :( > >(I don't have console access and the system is in a very remote location just >to make it extra fun) A console would make it easy. My suggestion is to keep a shell open in /rescue and use './sysctl' (and other commands in rescue). I think you will still be able to execute static executables in the current directory vis a relative path even if the FS is deadlocked. (As long as your shell isn't trying to write command history to a file). -- Peter Jeremy [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFF5nZa/opHv/APuIcRAkyIAJwKF73kAc3W6CMOq3e32ArAU50tSgCeM9s9 TrdkLuivuHdzt5hRUc4L9eg= =Yy19 -----END PGP SIGNATURE-----home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070301064442.GG837>