From nobody Thu Dec 14 22:32:21 2023 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 4SrnCs1nhrz53sGb for ; Thu, 14 Dec 2023 22:32:25 +0000 (UTC) (envelope-from ronald@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SrnCs1Fgyz3Fg1; Thu, 14 Dec 2023 22:32:25 +0000 (UTC) (envelope-from ronald@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1702593145; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=zMsOSAR5j/GbrzW2KmvGGFYBIJBy8+PZd0HXqRLFGyc=; b=V65Pt/Ovgh/JdLO9IUixjLFZmf9tuA/LZM52U6AZgOlRloYd4sfJ+sSlYRuZju/gJWvTxW UiJjlCymRpLPQtltsZQgPSB4h7CCnwvVi8DaCDEfT098oHdILT2w+XrF1z6TwlcX4XVjE2 QhWKY7ZEoAX5HIgygMy3BnyxjtQetkJv2cuI1+JEePnfUJW77YL7nevUG2cJ0AXV7K2YD3 5hHPBEYIywdaQTQFESyLQhSvdvIJS0pOdVAGAIA9QnUhhdVzLDXcc9LOAckzAa6L7rUM12 BfMdlr3RpHqRAMYT22RNWGkvhmkuaRtXfuFMO9DXw2qFhNlOPxfwgXgrhacipA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1702593145; a=rsa-sha256; cv=none; b=NgzFqcGm2L+SXQAzbcvDbfIBi0IGIdcRLjwx3Ce5Wtg/0c7rFjVCV+MN/SjY/cyjS8wZRl 4DjjHh4WFwsbtl/vEkCqxwHq0gOxoF3aExk2j/n+DUseONW2MFMtDEFJQyRcnf8erbI+Pm QuGd00DxVKDzqUE6YVc6LNWqrLTGFKKlOc3Q4NacGsJjI8M92JfWA7zb3y5CLLo66tACpS Rr+w30QJ1h/fNbocQT2tm0mZFUQHrF26fYz0GOF058dYf3+1L7ckJWogf3AX9DLLeUsxOP Q1F5UKayTky2TMqG47+1zKgF6FZ6vcj1soUE2WTxrVPCQP/KCy4BFqj9ZIqeiQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1702593145; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=zMsOSAR5j/GbrzW2KmvGGFYBIJBy8+PZd0HXqRLFGyc=; b=HgyF7Ey62mWWDZnUXBkQuj2eDw0sqwGaepAckv7hZqUoMn/6gXC8fyYq1mdjD7625435Wz CBhw+eXOx3m/D/X/vyrkyxvg/+mbBhNV/aQMh8bzHwfwXDvwkU4B09xCmHl9LqszUxrW01 7Ir09iZwhhMq/x4+vJ61FSbxfSlcGpr3wQ3q15h6n4ybkpN83TJBghNtAHmli97jLbGhzN tRrH6JpgWP6DTGAOpmH10x6CMfRBNfzapfoK4k3eKmRBc5pjp8EUhsd+LtJUWJA85nlneh hakjx7JaCDOsyJN1MOgHczRs+VOm484dRsHSgpT40HuqY2Q8B/WZZSVqnQgzLQ== Received: from [IPV6:2001:1c00:2709:2010:493e:9031:fcc0:f007] (2001-1c00-2709-2010-493e-9031-fcc0-f007.cable.dynamic.v6.ziggo.nl [IPv6:2001:1c00:2709:2010:493e:9031:fcc0:f007]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: ronald/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4SrnCr47tPzx20; Thu, 14 Dec 2023 22:32:24 +0000 (UTC) (envelope-from ronald@FreeBSD.org) Message-ID: <5fc39fab-3429-405b-9eac-1a7c94c3754f@FreeBSD.org> Date: Thu, 14 Dec 2023 23:32:21 +0100 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 User-Agent: Mozilla Thunderbird Subject: Re: unusual ZFS issue Content-Language: en-US To: Lexi Winter , Xin LI Cc: Pete Wright , "freebsd-fs@freebsd.org" References: <787CB64A-1687-49C3-9063-2CE3B6F957EF@le-fay.org> <1656A349-9E7D-4798-89D1-ECE39126FBC8@le-fay.org> From: Ronald Klop In-Reply-To: <1656A349-9E7D-4798-89D1-ECE39126FBC8@le-fay.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Did the IO error occur before or during the scrub? Regards, Ronald. On 12/14/23 23:29, Lexi Winter wrote: > On 14 Dec 2023, at 22:25, Xin LI wrote: >> Try "zpool status -x" and see if it would show something useful? > > the output seems to be the same as ‘zpool status -v’: > > # zpool status -xv > pool: data > state: ONLINE > status: One or more devices has experienced an error resulting in data > corruption. Applications may be affected. > action: Restore the file in question if possible. Otherwise restore the > entire pool from backup. > see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-8A > scan: scrub in progress since Thu Dec 14 18:58:21 2023 > 11.5T / 18.8T scanned at 962M/s, 8.71T / 18.8T issued at 726M/s > 0B repaired, 46.41% done, 04:02:02 to go > config: > > NAME STATE READ WRITE CKSUM > data ONLINE 0 0 0 > raidz2-0 ONLINE 0 0 0 > da4p1 ONLINE 0 0 0 > da6p1 ONLINE 0 0 0 > da5p1 ONLINE 0 0 0 > da7p1 ONLINE 0 0 0 > da1p1 ONLINE 0 0 0 > da0p1 ONLINE 0 0 0 > da3p1 ONLINE 0 0 0 > da2p1 ONLINE 0 0 0 > logs > mirror-2 ONLINE 0 0 0 > ada0p4 ONLINE 0 0 0 > ada1p4 ONLINE 0 0 0 > cache > ada1p5 ONLINE 0 0 0 > ada0p5 ONLINE 0 0 0 > > errors: Permanent errors have been detected in the following files: > > i think this is expected since -x just filters the output to show pools with errors? > > -x Only display status for pools that are exhibiting errors or are > otherwise unavailable. Warnings about pools not using the latest > on-disk format will not be included. > > thanks, lexi.