#3159: [kernel] PANIC: ASSERT FAILED: vnode->ref_count ==0 && vnode->busy -----------------------------+---------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1/Development Resolution: | Keywords: Blocked By: | Blocking: 8402, 8419 Has a Patch: 0 | Platform: All -----------------------------+---------------------------- Comment (by SeanCollins): If you have a b+tree error, this is fiarly easy to reproduce, not sure where the problem is, but if you load some apps, build up some pressure on the cache, and then invoke some disk i/o with file copying. It seems to pop up easily. In fact, just downloading the git repo, will often trigger this fialure. It seems like the mkdir command and expander and unzip really agitate this problem. Especially if you have a b+tree error in bfs. I frequently see this error during the unzip make image portion of building, but its gotten so bad lately on the 438xx series of nightlys, you can't even reliably build on haiku without some sort of kdl or app server crash, typically with a vfs.cpp assert failure. -- Ticket URL: <http://dev.haiku-os.org/ticket/3159#comment:9> Haiku <http://dev.haiku-os.org> Haiku - the operating system.