On Tue, Mar 18, 2025 at 2:40 PM Seyed Pouria Mousavizadeh Tehrani <
i...@spmzt.net> wrote:

> I created another pool and backed up all my data using rsync, which avoids
> block level cloning. It's working!
>

This probably has nothing to do with block cloning.

The assertion was that zap_increment() succeeded (0), while EIO (5) was
returned instead.  This is likely the result of data corruption with
correct checksums (in that case it's likely that you would see
ECKSUM=122).  When this happens, it's usually a permanent damage, the pool
should still be read-only importable but you can't revive it to read-write
state.  Common causes of this would be a permanent damage which could be
the result of a memory corruption (could be a bug in the kernel, or more
usually, faulty memory that was not detected or panicked your system
earlier).

> Should I create a PR for this issue on FreeBSD or OpenZFS github
> repository?
>
If you have a way to reliably trigger the issue please do file a FreeBSD PR
or open an issue at OpenZFS as it would be very useful.  Otherwise, it's
likely to be faulty memory and there is not a lot that can be done from
software.



>
> On 3/18/25 16:57, Dave Cottlehuber wrote:
>
> On Tue, 18 Mar 2025, at 12:35, Seyed Pouria Mousavizadeh Tehrani wrote:
>
> 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.<https://ibb.co/v6d4Kr7K> 
> <https://ibb.co/v6d4Kr7K>
>
> I'm using FreeBSD 15.0-CURRENT main-n275975-5963423232e8.
>
> 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
>
>
> --
> Seyed Pouria Mousavizadeh Tehrani
> Hoopad Cloud (AS214145)
>
>

Reply via email to