>Number:         656
>Category:       bin
>Synopsis:       BAD SUPER BLOCK messages from fsck
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    bin-bug-people (Utility Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Dec 25 19:20:03 1994
>Originator:     Thomas Eberhardt
>Organization:
CeVis, University of Bremen, Germany
>Release:        1.0A
>Environment:
	
System: NetBSD ed209 1.0A NetBSD 1.0A (ED209) #0: Mon Dec 26 01:53:10 MET 1994 thomas@ed209:/usr/src/sys/arch/i386/compile/ED209 i386

Machine: i386
>Description:
	After the file system code sync with CSRG I get this nasty message
	"BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST
	ALTERNATE" every time I reboot.  I've traced this back to a new
	dynamically changing field "fs_maxcluster" in the super block thats
	not copied to the alternate super block before comparison.
>How-To-Repeat:
	
>Fix:
*** sbin/fsck/setup.c-	Wed Dec 21 12:10:10 1994
--- sbin/fsck/setup.c	Mon Dec 26 04:08:07 1994
***************
*** 360,365 ****
--- 360,366 ----
  	altsblock.fs_optim = sblock.fs_optim;
  	altsblock.fs_rotdelay = sblock.fs_rotdelay;
  	altsblock.fs_maxbpg = sblock.fs_maxbpg;
+ 	altsblock.fs_maxcluster = sblock.fs_maxcluster;
  	memcpy(altsblock.fs_csp, sblock.fs_csp,
  		sizeof sblock.fs_csp);
  	memcpy(altsblock.fs_fsmnt, sblock.fs_fsmnt,
>Audit-Trail:
>Unformatted: