>Number:         8185
>Category:       port-alpha
>Synopsis:       ffs_valloc: dup alloc panic in single user mode.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    port-alpha-maintainer (NetBSD/alpha Portmaster)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Aug 10 10:05:01 1999
>Last-Modified:
>Originator:     Darren Reed
>Organization:
>Release:        NetBSD-1.4
>Environment:
System: NetBSD ghalahad.reed.wattle.id.au 1.4 NetBSD 1.4 (GERNERIC) #0 alpha


>Description:
	THe following sequence led to a kernel panic:
# mount -u /
/dev/wd0a: file system not clean (fs_flags=20); please fsck(8)
# fsck -p /
/dev/rwd0a: UNREF FILE I=4  OWNER=root MODE=100600
/dev/rwd0a: SIZE=0 MTIME=Aug 11 02:37 2019  (CLEARED)
/dev/rwd0a: FREE BLK COUNT(S) WRONG IN SUPERBLK (SALVAGED)
/dev/rwd0a: BLK(S) MISSING IN BIT MAPS (SALVAGED)
/dev/rwd0a: SUMMARY INFORMATION BAD (SALVAGED)
/dev/rwd0a: 1023 files, 22171 used, 41676 free (108 frags, 5196 blocks, 0.2% fragmentation)
/dev/rwd0a: MARKING FILE SYSTEM CLEAN
# fsck -p /usr
/dev/rwd0d: 33162 files, 409607 used, 547255 free (8215 frags, 67380 blocks, 0.9% fragmentation)
/dev/rwd0d: MARKING FILE SYSTEM CLEAN
# mount /usr
# cd /etc
# vi ttys
WARNING: TERM environment variable not set.
mode = 0100600, inum = 4, fs = /
panic: ffs_valloc: dup alloc
Stopped in vi at        Debugger+0x4:   ret     zero,(ra)
db>

whilst "-p" might be somewhat to blame here, the above is inline with
what a normal reboot would lead to happen, I believe.
>How-To-Repeat:
	
>Fix:
	
>Audit-Trail:
>Unformatted: