[issue1125] panic: assertion: iou->io.lock.refs == 0 in hammer_io_inval

Thomas Nikolajsen sinknull at crater.dragonflybsd.org
Mon Sep 8 13:26:23 PDT 2008


Thomas Nikolajsen <thomas.nikolajsen at mail.dk> added the comment:

I have no problem reproducing this panic.

Generated another crash dump using GENERIC kernel
(might be easier to debug: HAMMER not loaded as module):
Crash dump on leaf in crash/hammer/ask/*.11.

Also tried another host as nfs server: minimal setup:
 - fresh HAMMER file system, with just one PFS (#1)
 - data for /usr/src cpdup'ed from other nfs server
 - empty /usr/obj
 - more RAM (512MB vs 128MB)
Got same panic, after a few minutes of buildworld;
crash dump avail. on request (200MB).

It seems like I get this panic when using write intensive operations
on nfs mounts. Read mostly operations doesn't trigger bug.

----------
priority:  -> bug

_____________________________________________________
DragonFly issue tracker <bugs at lists.dragonflybsd.org>
<https://bugs.dragonflybsd.org/issue1125>
_____________________________________________________





More information about the Bugs mailing list