Issue #3055 has been updated by arc...@b1t.name.
Filesystem was close to 90% full with 20% being "jettissonable". I'm not sure about this one actually as FS was created more then a few weeks ago and can contain some older discrepancies. I can recreate FS from scratch and retest if that would be required. Anyway double "hammer cleanup" makes FS stable again. Without cleanup host can't even boot due to problems writing data: strategy_xop_write: error 32 loff=0000000057480000 strategy_xop_write: error 32 loff=00000000583f0000 strategy_xop_write: error 32 loff=000000005a680000 strategy_xop_write: error 32 loff=0000000063f50000 strategy_xop_write: error 32 loff=00000000677c0000 strategy_xop_write: error 32 loff=000000006aa90000 strategy_xop_write: error 32 loff=0000000073020000 strategy_xop_write: error 32 loff=0000000076cf0000 strategy_xop_write: error 32 loff=000000007f660000 strategy_xop_write: error 32 loff=0000000084430000 strategy_xop_write: error 32 loff=0000000087450000 strategy_xop_write: error 32 loff=0000000088e00000 strategy_xop_write: error 32 loff=0000000093ac0000 strategy_xop_write: error 32 loff=0000000093b90000 Or just crashes again. ---------------------------------------- Bug #3055: HAMMER2 crash + LK_RELEASE fail http://bugs.dragonflybsd.org/issues/3055#change-13202 * Author: arc...@b1t.name * Status: In Progress * Priority: Normal * Assignee: dillon * Category: VFS subsystem * Target version: ---------------------------------------- This happens when 'cleanup' was too long ago. kern_rename actually happened hours before before the actual crash. ---Files-------------------------------- core.txt.33 (178 KB) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
