From nobody Sat Sep 25 22:00:59 2021 X-Original-To: freebsd-fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id AE00217CD322 for ; Sat, 25 Sep 2021 22:01:11 +0000 (UTC) (envelope-from SRS0=/8x4=OP=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4HH2sg3vj7z3m6H for ; Sat, 25 Sep 2021 22:01:11 +0000 (UTC) (envelope-from SRS0=/8x4=OP=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 8FB2828417; Sun, 26 Sep 2021 00:01:03 +0200 (CEST) Received: from illbsd.quip.test (ip-78-45-215-131.net.upcbroadband.cz [78.45.215.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 6C79C28411; Sun, 26 Sep 2021 00:01:00 +0200 (CEST) Subject: Re: ZFS errors with two HEX numbers. To: Zaphod Beeblebrox , freebsd-fs References: From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <33176b34-6929-57fb-2e3f-bd3e9396fe01@quip.cz> Date: Sun, 26 Sep 2021 00:00:59 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@freebsd.org MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4HH2sg3vj7z3m6H X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On 25/09/2021 21:28, Zaphod Beeblebrox wrote: > I've got a ZFS pool --- 3 x 8 x 4T disks in a RAIDZ2 configuration. Every > few months I scrub them. This time, curiously, it came up with an error. > All the disks in a vdev simultaneously give an error when this is > scanned.... thusly: > > raidz2-3 ONLINE 0 0 0 > gpt/v1-f0 ONLINE 0 0 1 > gpt/v1-f1 ONLINE 0 0 1 > gpt/v1-f2 ONLINE 0 0 1 > gpt/v1-f3 ONLINE 0 0 1 > gpt/v1-f4 ONLINE 0 0 1 > gpt/v1-f5 ONLINE 0 0 1 > gpt/v1-f6a ONLINE 0 0 1 > gpt/v1-f7b ONLINE 0 0 1 > > ... and if I add -v to the status, I see the following right now: > > errors: Permanent errors have been detected in the following files: > <0x57b2>:<0x73ab46> > > Now... since that happened, I have scrubbed twice more. The first number > changes each time. Last scrub it was: <0x4223>:<0x73ab46>. Note the last > number is not changing. > > I have done some googling and found that this might be something that got > corrupted on delete or somesuch. My OCD would like to know what 0x4223 > maps to (or now 0x57b2) s.t. I could find it and remove it. I _think_ this > is a snapshot reference? I have seen this in the past. It was corruption on some deleted file preserved on snapshot. Once I deleted snapshots this error disappeared. [...] Miroslav Lachman