From owner-freebsd-hackers Sun Jan 4 09:46:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA10506 for hackers-outgoing; Sun, 4 Jan 1998 09:46:23 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id JAA10478 for ; Sun, 4 Jan 1998 09:46:14 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: by iafnl.es.iaf.nl with UUCP id AA32720 (5.67b/IDA-1.5 for hackers@FreeBSD.ORG); Sun, 4 Jan 1998 18:46:09 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.7/8.6.12) id OAA00895; Sun, 4 Jan 1998 14:46:52 +0100 (MET) From: Wilko Bulte Message-Id: <199801041346.OAA00895@yedi.iaf.nl> Subject: Re: Process wedge in 'inode' To: toor@dyson.iquest.net (John S. Dyson) Date: Sun, 4 Jan 1998 14:46:52 +0100 (MET) Cc: mike@smith.net.au, hackers@FreeBSD.ORG In-Reply-To: <199801040815.DAA11966@dyson.iquest.net> from "John S. Dyson" at Jan 4, 98 03:15:58 am X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk As John S. Dyson wrote... > Mike Smith said: > > > > Just simultaneously checking out two copies of the kernel source using > > 'cvs co sys', I have an interesting situation: > > > > kingsford:~>ps axlwww > > UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND > > 1000 1359 1348 1 -14 0 1356 864 inode D+ v1 0:06.84 cvs co sys > > 1000 1366 160 4 -14 0 1356 812 inode D+ v2 0:06.77 cvs co sys > > > > Neither process is responding to signals, and neither can be killed. > > The rest of the system is running as normal... > > > > This is -current as of 971220. > > > Yep, as I have said, I broke -current, and *please* expect it to problematical. > The issues that I have been working are very complex and tedious, but the > end result will be advantageous beyond even what I had expected. I am > within a few hours/days of commiting the corrected code, and please back up to > code before my commit. I do have test suites that expose the problems, and > any usage of the erroneous code will lead to nowhere except frustration. > > You'll have nothing but trouble with the code, including accumulation of > disk blocks, crashes, and file corruption. Please do not use -current right > now. I have been working 18Hrs/day on the stuff, even forgoing dates with > an extremely attractive female friend of mine, and the approach that I Oh oh... This is really getting out of hand... ;-) (could not resist..) _ ______________________________________________________________________ | / o / / _ Bulte email: wilko @ yedi.iaf.nl http://www.tcja.nl/~wilko |/|/ / / /( (_) Arnhem, The Netherlands - Do, or do not. There is no 'try' ---------------- Support your local daemons: run [Free,Net]BSD Unix ------