Re: panic in 5.2-CURRENT-20040807-SESNAP

--- Martin Blapp <mb_at_imp.ch> wrote:
> Hi,
> 
> > panic: ffs_clusteralloc: map mismatch
> > cpuid = 0;
> > KDB: enter: panic
> > [thread 100113]
> > Stopped at     kdb_enter+0x2b: nop
> > db>
> >
> 
> I've got the same panic with a 5.2.1 RELEASE yesterday. To get
> a backtrace, type "trace" or "where". Then we can see more.

panic: ffs_clusteralloc: map mismatch
cpuid = 0;
KDB: enter: panic
[thread 100113]
Stopped at     kdb_enter+0x2b: nop
db>
db> trace
kdb_enter(c07ef0b8) at kdb_enter+0x2b
panic(c08030d1,b7d00,0,30,0) at panic+0x131
ffs_clusteralloc(c1d477a8,2,322,0,3) at ffs_clusteralloc+0x303
ffs_hashalloc(c1d477a8,2,2f820,0,3) at ffs_hashalloc+0x28
ffs_reallocblks_ufs2(c86b0b54,c86b0b70,c0644c70,c86b0b54,c86b0ae0) at
ffs_reallocblks_ufs2+0x34a
ffs_reallocblks(c86b0b54) at ffs_reallocblks+0x36
cluster_write(c3a45ec4,34000,0,3) at cluster_write+0x25c
ffs_write(c86b0c14) at ffs_write+0x50c
vn_write(c16ad088,c86b0c88,c16aae80,0,c1760420) at vn_write+0x1f8
dofilewrite(c1760420,c16ad088,3,8300000,2b58) at dofilewrite+0xa8
write(c1760420,c86d0d14,3,35,296) at write+0x39
syscall(2f,2f,2f,80e8c40,80e8c40) at syscall+0x217
Xint0x80_syscall() at Xint0x80_syscall+0x1f
--- syscall (4, FreeBSD ELF32, write), eip = 0x80b5f77, esp =
0xbfbfe6fc, ebp = 0xbfbfe718 ---
db>

The "where" command produced the same result.


		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail