... and a fine time was had by all. Fsck, fsck, fsck!

Somehow one of the filesystems in my FreeBSD box got hosed just enough
to cause a panic:

reboot after panic: ffs_blkfree: freeing free block

This started today, I know not why, after continuous months of uptime.

Happiness, whatever it may be, is *NOT* running fsck and seeing an
INTERNAL ERROR message due to something hosed in softupdates.

I now understand single user mode rather better than I want to. I do
*NOT* understand why fsck would not clean up /home and /usr properly and
MARK THEM DAMNIT CLEAN. AAAAAAAAARRRRRRRRRRRRRRRRRGGGGGHHHHHHHHHHHHH!

--
[...] the periodic and predictable system failures were a result of one part of
the system expecting the clock to count 1024 ticks per unit time, while the
other part thought the clock was counting 1000 ticks per unit time.
-- me in asr, on the Patriot missile system
.

Relevant Pages

  • Re: Well ... _Pfui_!
    ... airlines which are in a negative profit situation (he quotes PanAm ... other part thought the clock was counting 1000 ticks per unit time. ...
    (alt.sysadmin.recovery)
  • Re: I have been CHALLENGED. . .
    ... all library-bound and signed by the author: library discards. ... other part thought the clock was counting 1000 ticks per unit time. ...
    (alt.sysadmin.recovery)
  • Re: I have been CHALLENGED. . .
    ... It weighs half a ton, has no brakes or lights, and looks like it's just been ... other part thought the clock was counting 1000 ticks per unit time. ...
    (alt.sysadmin.recovery)
  • Re: Scottish, uhm... uuh... what should we call this?
    ... the system expecting the clock to count 1024 ticks per unit time, ... other part thought the clock was counting 1000 ticks per unit time. ...
    (alt.sysadmin.recovery)
  • Re: The Sheer Stupididty of SR
    ... to ticks (cycles, periods, whatever) of one oscillator compared to ... The observer, who has an identical clock, receives N ticks per second ...
    (sci.physics.relativity)