While doing some stuff I ran into an 'fsck' problem which seems to be
very old. I don't know if it's VAX-specific or not..

I was trying out 1.3F with UVM on my 3600 (KA650) and it died booting with a
malloc failure and dumped me in the debugger. 

I then rebooted using 1.3E and it started checking my root FS.

All went well until it came to the 'fix bitmap' stage. Then fsck 
got a segmentation-fault and dumped core. :-(

Oh dear.. Now what?

I suspected the 'fsck' binary I compiled myself, so I grabbed a
binary from a 1.2 tarball I have and ran that.

To my surprise it died at the same spot!!

I even went back as far as 1.1A and it did the same...

I finally got the disk cleaned by running fsck and then _only_ answering
'yes' to the first question. After 5 or so fsck's the partition 
was clean once more.

So it seems that one of the earlier stages (blocks/pathnames) in fsck
causes some buffer overruns/stack corruption which in turn causes stuff in 
stages 5 and higher to segfault.

Anyone seen this before?

							Bye Arno.

-- 
Internet Exchange Europe B.V.Fax: +31-70-3630470 | One disk to rule them all,
Lange Voorhout 9             Tel: +31-70-3600379 | One disk to bind them,
2514EA Den Haag +--------------------------------+ One disk to hold the files
The Netherlands |   * MUSICAL INTERLUDE   *      | And in the darkness grind 'em
----------------+--------------------------------+------------------------------

 We say Retribution, We say Vengeance is bliss, We say Revolution,
 With a Cast-Iron fist!                  (Megadeth, 'The Disintegrators')

--------------------------------------------------------------------------------