https://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082017-09-14T19:37:19ZDragonFlyBSD bugtrackerDragonFlyBSD - Bug #3055: HAMMER2 crash + LK_RELEASE failhttps://bugs.dragonflybsd.org/issues/3055?journal_id=132002017-09-14T19:37:19Zarcade@b1t.namearcade@b1t.name
<ul></ul><p>PS: This is without latest kern_mutex.c changes.</p> DragonFlyBSD - Bug #3055: HAMMER2 crash + LK_RELEASE failhttps://bugs.dragonflybsd.org/issues/3055?journal_id=132012017-09-14T20:36:32Zdillon
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>Assignee</strong> set to <i>dillon</i></li></ul><p>Was the filesystem full at the time this ran? There is an error path that is not being checked properly in hammer2_chain_indirect_maintenance() for the situation where the filesystem has become full. I will commit error processing for that part of the code right now. If it still panics (verses just thowing an error on the kernel console), I'll need a backtrace from kgdb.</p>
<p>-Matt</p> DragonFlyBSD - Bug #3055: HAMMER2 crash + LK_RELEASE failhttps://bugs.dragonflybsd.org/issues/3055?journal_id=132022017-09-14T21:41:04Zarcade@b1t.namearcade@b1t.name
<ul></ul><p>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.</p>
<p>Anyway double "hammer cleanup" makes FS stable again. Without cleanup host can't even boot due to problems writing data:</p>
<p>strategy_xop_write: error 32 loff=0000000057480000<br />strategy_xop_write: error 32 loff=00000000583f0000<br />strategy_xop_write: error 32 loff=000000005a680000<br />strategy_xop_write: error 32 loff=0000000063f50000<br />strategy_xop_write: error 32 loff=00000000677c0000<br />strategy_xop_write: error 32 loff=000000006aa90000<br />strategy_xop_write: error 32 loff=0000000073020000<br />strategy_xop_write: error 32 loff=0000000076cf0000<br />strategy_xop_write: error 32 loff=000000007f660000<br />strategy_xop_write: error 32 loff=0000000084430000<br />strategy_xop_write: error 32 loff=0000000087450000<br />strategy_xop_write: error 32 loff=0000000088e00000<br />strategy_xop_write: error 32 loff=0000000093ac0000<br />strategy_xop_write: error 32 loff=0000000093b90000</p>
<p>Or just crashes again.</p> DragonFlyBSD - Bug #3055: HAMMER2 crash + LK_RELEASE failhttps://bugs.dragonflybsd.org/issues/3055?journal_id=132062017-09-18T16:07:53Zarcade@b1t.namearcade@b1t.name
<ul><li><strong>File</strong> <a href="/attachments/1418">core.txt.34</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/1418/core.txt.34">core.txt.34</a> added</li></ul><p>Happened again. Alas, my kernel was built without DEBUG so kgdb output is pretty useless. Will try replicating one more time.</p> DragonFlyBSD - Bug #3055: HAMMER2 crash + LK_RELEASE failhttps://bugs.dragonflybsd.org/issues/3055?journal_id=132352017-09-23T21:52:04Zarcade@b1t.namearcade@b1t.name
<ul><li><strong>File</strong> <a href="/attachments/1433">core.txt.38</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/1433/core.txt.38">core.txt.38</a> added</li></ul><p>Happened again. Pool was 93% full (9G free).</p> DragonFlyBSD - Bug #3055: HAMMER2 crash + LK_RELEASE failhttps://bugs.dragonflybsd.org/issues/3055?journal_id=132652017-10-12T08:12:15Zarcade@b1t.namearcade@b1t.name
<ul><li><strong>File</strong> <a href="/attachments/1448">core.txt.40</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/1448/core.txt.40">core.txt.40</a> added</li><li><strong>File</strong> <a href="/attachments/1447">core.txt.39</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/1447/core.txt.39">core.txt.39</a> added</li></ul><p>A few more crashes. 7G free space reached...</p> DragonFlyBSD - Bug #3055: HAMMER2 crash + LK_RELEASE failhttps://bugs.dragonflybsd.org/issues/3055?journal_id=132702017-10-14T22:12:51Zdillon
<ul></ul><p>I think I see what is going on. I did not completely instrument error handling for some of these failure cases (when the media becomes full). Several calls to hammer2_chain_delete() are not processing the returned error code and that may be leading to these assertions.</p>
<p>I am working on instrumenting these and will commit an update this afternoon to master and release.</p>
<p>-Matt</p> DragonFlyBSD - Bug #3055: HAMMER2 crash + LK_RELEASE failhttps://bugs.dragonflybsd.org/issues/3055?journal_id=132742017-10-17T20:21:45Zarcade@b1t.namearcade@b1t.name
<ul><li><strong>File</strong> <a href="/attachments/1451">core.txt.44</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/1451/core.txt.44">core.txt.44</a> added</li></ul><p>Another crash...</p> DragonFlyBSD - Bug #3055: HAMMER2 crash + LK_RELEASE failhttps://bugs.dragonflybsd.org/issues/3055?journal_id=133012017-10-28T23:15:42Zarcade@b1t.namearcade@b1t.name
<ul></ul><p>This situation was triggered a few times more, but there was no crash. Host was getting slow but was slowly gettin through.</p> DragonFlyBSD - Bug #3055: HAMMER2 crash + LK_RELEASE failhttps://bugs.dragonflybsd.org/issues/3055?journal_id=133022017-11-01T21:14:31Zarcade@b1t.namearcade@b1t.name
<ul><li><strong>File</strong> <a href="/attachments/1470">core.txt.46</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/1470/core.txt.46">core.txt.46</a> added</li></ul><p>I knew I can did it.</p> DragonFlyBSD - Bug #3055: HAMMER2 crash + LK_RELEASE failhttps://bugs.dragonflybsd.org/issues/3055?journal_id=133032017-11-02T03:22:17Zarcade@b1t.namearcade@b1t.name
<ul><li><strong>File</strong> <a href="/attachments/1471">core.txt.47</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/1471/core.txt.47">core.txt.47</a> added</li></ul><p>And here's something new:</p>
<p>panic: assertion "chain->bref.key == base[i].key" failed in hammer2_combined_find at /usr/src/sys/vfs/hammer2/hammer2_chain.c:4968</p> DragonFlyBSD - Bug #3055: HAMMER2 crash + LK_RELEASE failhttps://bugs.dragonflybsd.org/issues/3055?journal_id=133282017-11-28T08:13:51Zarcade@b1t.namearcade@b1t.name
<ul><li><strong>File</strong> <a href="/attachments/1489">core.txt.51</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/1489/core.txt.51">core.txt.51</a> added</li><li><strong>File</strong> <a href="/attachments/1490">core.txt.52</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/1490/core.txt.52">core.txt.52</a> added</li></ul><p>Fresh cores arrived.</p> DragonFlyBSD - Bug #3055: HAMMER2 crash + LK_RELEASE failhttps://bugs.dragonflybsd.org/issues/3055?journal_id=136962019-06-18T14:38:56Zliweitianuxliweitianux@live.com
<ul></ul><p>Hello. Is this issue resolved with the latest master/release? The HAMMER2 has gained significant improvements. Thank you.</p> DragonFlyBSD - Bug #3055: HAMMER2 crash + LK_RELEASE failhttps://bugs.dragonflybsd.org/issues/3055?journal_id=140902021-05-27T08:18:29Zarcade@b1t.namearcade@b1t.name
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Closed</i></li></ul><p>I guess not applicable anymore.</p>