Date: Tue, 18 Mar 2025 11:45:13 -0400 From: Alexander Motin <mav@FreeBSD.org> To: Seyed Pouria Mousavizadeh Tehrani <info@spmzt.net> Cc: freebsd-current@freebsd.org Subject: Re: zap_increment panic on specific zpool Message-ID: <300d5510-7c0d-464f-8526-6a7255780bee@FreeBSD.org> In-Reply-To: <4344133F-234B-432D-A373-792CCBA0213D@spmzt.net> References: <887C8BE0-9670-4892-9B60-9CA09675D40C@spmzt.net> <1d0ea40b-82a3-40c6-ada6-b3034ec0d362@FreeBSD.org> <4344133F-234B-432D-A373-792CCBA0213D@spmzt.net>
index | next in thread | previous in thread | raw e-mail
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 Motinhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?300d5510-7c0d-464f-8526-6a7255780bee>