RE: Defcon Bill

Joe Barrera (
Wed, 22 Apr 1998 12:36:51 -0700

> I fail to see a connexion between a file-system error and a total
> O.S. meltdown. Perhaps a better analogy would be "kernel panic".

Duh, well, "freeing free inode" is a fatal kernel panic.

Why do I get the bad feeling that I've forgotten more about Unix than most
of you know?

At any rate, when searching the web for information about panics, I found
the following book on Sun's recommended book list:


"The phone rings and you answer. A user says his terminal is dead. As soon
as you hang up, you receive another call and another complaint about no
response from the computer. Ignoring the next call, you get to the computer
console just in time to see the word 'Panic' scroll off the top of the
screen. Another message says something about 'dumping', and now the system
appears to be rebooting itself.

"What happened?

"UNIX systems 'panic'. It's a fact of life. Depending on the hardware and
software involved, some systems panic rather frequently, some once in a blue
moon, some never.

"What causes panics? What is happening when you see the 'dumping' message?
How can you find the source of troubles and get the system back on-line and
into working condition?
This book answers those questions and many more.

> Imagine if I tried to work on some piece of crap that you and your
> masters are pushing... I'd be dead in a week.

What an interesting theory -- one that clearly calls for an experiment. I'll
send a system out to you overnight.

- Joe

P.S. ObAmazonURL:

<li> <a
Panic! : Unix System Crash Dump Analysis</a> by Chris Drake, Kimberely

Joseph S. Barrera III <>
Phone, Office: (415) 778-8227; Cellular: (415) 601-3719; Home: (650)
The opinions expressed in this message are my own personal views and do not
reflect the official views of Microsoft Corporation.

How young are you?
How old am I?
Let's count the rings
Around my eyes...
- The Replacements