Re: zap_increment panic on specific zpool

On 18.03.2025 11:32, Seyed Pouria Mousavizadeh Tehrani wrote:
> New link:
> <https://imgur.com/a/a3ClXYL <https://imgur.com/a/a3ClXYL>>

It looks like a metadata corruption in user quota handling, and the code 
is obviously not written to handle it, asserting instead.  Without 
deeper look I am not ready to say whether it was not expected to ever 
happen, impossible/difficult to handle at that place, or somebody was 
just lazy.  I'd recommend you to check system memory and other hardware 
for errors to reduce chance of further corruptions, and probably 
evacuate the data while importing the pool as read-only, which should 
not access or at least update the quotas.

-- 
Alexander Motin