> 	When fsck performs sanity checks against the super block of a file system,
> it does a comparison of the primary super block against the backup copy
> located in the final cylinder group of the file system.  If the comparison
> fails, fsck requests that the user use the -b flag to specify an alternate
> copy of the super block in order to restore the primary super block.  If
> the primary super block is corrupt, then it will be accurately updated at
> the end of the fsck -b.  The fsck -b procedure, however, does not update
> the last copy of the super block in the filesystem.  Thus, even if the
> primary super block is correct, the next "fsck" will fail with the same
> error.

This I have seen. I could not "fix" the filesystem, and gave up by backing
it up (mounted "dirty") and the newfs'ing it, and restoring. Not fun.

If you can fix this...

Regards,
-- 
Peter Galbavy					work: peter@demon.net
Wonderland					rest: peter@wonderland.org
						play: http://www.wonderland.org/
"The 'net interprets censorship as damage and routes around it." - John Gilmore