Re: zap_increment panic on specific zpool

From: Seyed Pouria Mousavizadeh Tehrani <info_at_spmzt.net>
Date: Tue, 18 Mar 2025 21:39:43 UTC 
<!DOCTYPE html>
<html style="direction: ltr;">
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
    <style id="bidiui-paragraph-margins" type="text/css">body p { margin-bottom: 0cm; margin-top: 0pt; } </style>
  </head>
  <body bidimailui-charset-is-forced="true"
    bidimailui-detected-decoding-type="UTF-8">
    <p>I created another pool and backed up all my data using rsync,
      which avoids block level cloning. It's working!<br>
      <br>
      &gt; you may be able to boot again using either a RELEASE if your
      zpool hasn't been upgraded past that point, or a GENERIC-NODEBUG
      from CURRENT.<br>
      I'm using GENERIC-NODEBUG. Thank you anyway!</p>
    <p><br>
    </p>
    <p>Should I create a PR for this issue on FreeBSD or OpenZFS github
      repository?<br>
    </p>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 3/18/25 16:57, Dave Cottlehuber
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:d783ac35-1bb5-43cf-a426-ecfec54f14b4@app.fastmail.com">
      <pre wrap="" class="moz-quote-pre">On Tue, 18 Mar 2025, at 12:35, Seyed Pouria Mousavizadeh Tehrani wrote:
</pre>
      <blockquote type="cite">
        <pre wrap="" class="moz-quote-pre">Hi, 

I was working on my desktop when it suddenly panicked, and Now, I'm 
unable to boot into multi-user mode anymore. Additionally, in single 
user-mode with my bpool, whenever I execute the "zpool import it 
rpool", the panic occurs shortly after.

My kdb backtrace log is attached to this url.
<a class="moz-txt-link-rfc2396E" href="https://ibb.co/v6d4Kr7K">&lt;https://ibb.co/v6d4Kr7K&gt;</a>

I'm using FreeBSD 15.0-CURRENT main-n275975-5963423232e8.
</pre>
      </blockquote>
      <pre wrap="" class="moz-quote-pre">
This looks like an assert; you may be able to boot again using
either a RELEASE if your zpool hasn't been upgraded past that
point, or a GENERIC-NODEBUG from CURRENT. This would at least get
you working, but it won't fix the underlying cause.

hope it helps,
A+
Dave

</pre>
    </blockquote>
    <pre class="moz-signature" cols="72">-- 
Seyed Pouria Mousavizadeh Tehrani
Hoopad Cloud (AS214145)
</pre>
  </body>
</html>