Is it me fsck'ing up, or is fsck(8) lacking behind in the
dirpref changes?
Automatic boot in progress...
/dev/da0s1a: BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST
ALTERNATE
/dev/da0s1a: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
/dev/da0s1a: Automatic file system check failed . . . help!
Enter full pathname of shell or RETURN for /bin/sh:
# fsck_ffs -b 32 /
Alternate super block location: 32
** /dev/da0s1a
** Last Mounted on
** Root file system
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
FREE BLK COUNT(S) WRONG IN SUPERBLK
SALVAGE? [yn] y
2683 files, 136083 used, 399724 free (1164 frags, 49820 blocks, 0.2% fragmentation)
UPDATE STANDARD SUPERBLOCK? [yn] y
***** FILE SYSTEM WAS MODIFIED *****
Wonder if we should have seen something like this:
http://www.openbsd.org/cgi-bin/cvsweb/src/sbin/fsck_ffs/setup.c.diff?r1=1.8&r2=1.9&f=h
BTW, the box then panic'ed right after going multiuser, but
I dunno if thats related (managed to get it running on kernel.old):
Fatal trap 12: page fault while in kernel mode
cpuid = 1; lapic.id = 00000000
fault virtual address = 0x4
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc021ebda
stack pointer = 0x10:0xdfa6ec20
frame pointer = 0x10:0xdfa6ec30
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 319 (named)
kernel: type 12 trap, code=0
CPU1 stopping CPUs: 0x00000001... stopped.
Stopped at ffs_valloc+0x8e: cmpb $0,0(%edi,%eax,1)
db> trace
ffs_valloc(dabeb1c0,81a4,c1c54500,dfa6ec58,dfa6edb8) at ffs_valloc+0x8e
ufs_makeinode(81a4,dabeb1c0,dfa6eea4,dfa6eeb8) at ufs_makeinode+0x61
ufs_create(dfa6edb8,dfa6ee2c,c01bd59f,dfa6edb8,dfa6ef80) at ufs_create+0x2b
ufs_vnoperate(dfa6edb8,dfa6ef80,0,3,a02) at ufs_vnoperate+0x15
vn_open(dfa6ee90,dfa6ee5c,1a4,d9d40100,0) at vn_open+0x177
open(d9d40100,dfa6ef80,8114366,80eb062,0) at open+0xd6
syscall(2f,2f,2f,0,80eb062) at syscall+0x405
syscall_with_err_pushed() at syscall_with_err_pushed+0x1b
/Niels Chr.
--
Niels Christian Bank-Pedersen, NCB1-RIPE.
"Hey, are any of you guys out there actually *using* RFC 2549?"
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message