I just got this panic on a recent 2.5.1
System is DragonFly v2.5.1.631.g711a0-DEVELOPMENT from 2010-01-22 running on a
Core 2 Duo system with 2GB RAM
The machine is a NFS server for pkgsrc distfiles.
It was extracting a distfile locally and a NFS client was also extracting a
different distfile when the panic occurred.
The filesystem is a Hammer v4 volume created recently. It is not an upgrade of
a previous hammer version:
Filesystem Size Used Avail Capacity Mounted on
SAMSUNG.160 144G 22G 122G 16% /
A brief transcription of the panic message:
panic: cleaned vnode isn't
mp_lock = 00000001; cpuid = 1
Trace beginning at
panic
panic
allocvnode
getnewvnode(
hammer_get_vnode
hammer_vop_ncreate
vop_ncreate
vn_open
kern_open
sys_open
syscall2
Xint0x80_syscall
Debugger("panic")
CPU1 stopping CPUs: 0x00000001
stopped
db>
Even though I entered "call dumpsys" on the db prompt, there was no crash dump
after the next boot.
--
Francois Tigeot