From nobody Sun Sep 26 04:25:57 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 1549017CCADB for ; Sun, 26 Sep 2021 04:26:13 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-ed1-x52e.google.com (mail-ed1-x52e.google.com [IPv6:2a00:1450:4864:20::52e]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HHCPw4qKYz4ljR; Sun, 26 Sep 2021 04:26:12 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: by mail-ed1-x52e.google.com with SMTP id l8so5850555edw.2; Sat, 25 Sep 2021 21:26:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2unzDKT8fbjL3d3lsMgA5oMKEDcagcItr1K7v5pJv04=; b=RmdN/EDGUIFSe3Ssrcm0vHW0d1CWNfrLyRbvlXZAsTFEpKcwnjJlZpwsIGjixEs1Vy PQ0LZalXOOX3m/k6lcABALfKWg7ELAB8DYMQntvTYGeyD1bs/BaIBf+kq5ywn2P71y2B VDBeyHsbIrSYRfMaNRZmLBTTEg5TMNKaGXkdjCyIxFhZp2Uiy9lQVsbxigafcfFbBN6+ 08bo6oNh3Y3oVYt6fbDffUF4He/ZJDg38vmSfnC6XwbbI0yYham4cX2xHqmJRHnDcege MXIDHL6rt8jLNeBQYPsNsBl2y5t6QkWna/Px5hAeKSljAccAe8ilYutm3Se1RBugAPeJ ySEw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2unzDKT8fbjL3d3lsMgA5oMKEDcagcItr1K7v5pJv04=; b=8AZv1k7dmQ2i1dy6e4QajKPca8pFLb+wTSDeE3/gRmItRLS/73Qd5qoQXNeVy7iwa6 qqiPh+mP8/Slu+IrXCXQYWzJOSpfHlypzsM4RId6cjzRzcMfaalgEgjo9qOFYh50kBI4 KcG+ckQdHnNRUylqVzdkrxNrk3n0vLWXQ/7baxq5mN21lbDoU3q0MeYeiKdEGJ/8Dugd rROIH+0S8vx9bc0q1SrDQrz1zneZtHIDeOOxJOPy92qs6hkzDVHISAz7QkWQG/TKErKQ xo66l8OKs3EEveMRSTVbJHIhXYrK87PtikDyZvfrCpQHYZlDEa3yx+t3osT3oJIrL0jO rKHw== X-Gm-Message-State: AOAM531GnQ3hZpTFxthVBkONAMqjE1U5QubgktikUqTWCIzdb7d5D4Sg Ao216kPKejcabnNUVqCaSE2rBiv/tjHLUIScJD+hvGA= X-Google-Smtp-Source: ABdhPJxvFveySBcKD4tFuda0vjKUohWcQ0aqIWeNE+U8ydCJlhWcEN4DcxP+xBp2pGyRw4dv5azpACEihlk0ELXVKQU= X-Received: by 2002:a17:906:c205:: with SMTP id d5mr20469141ejz.74.1632630370184; Sat, 25 Sep 2021 21:26:10 -0700 (PDT) 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 References: <33176b34-6929-57fb-2e3f-bd3e9396fe01@quip.cz> In-Reply-To: From: Zaphod Beeblebrox Date: Sun, 26 Sep 2021 00:25:57 -0400 Message-ID: Subject: Re: ZFS errors with two HEX numbers. To: Alan Somers Cc: Miroslav Lachman <000.fbsd@quip.cz>, freebsd-fs Content-Type: multipart/alternative; boundary="00000000000043b10605ccde6151" X-Rspamd-Queue-Id: 4HHCPw4qKYz4ljR X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: Y --00000000000043b10605ccde6151 Content-Type: text/plain; charset="UTF-8" I looked through sysctl kstat.zfs --- Neither number appears. Is there some similar way I can list snapshots? I thought ZFS listed snapshots when listing them here...? On Sat, Sep 25, 2021 at 7:20 PM Alan Somers wrote: > On Sat, Sep 25, 2021 at 4:01 PM Miroslav Lachman <000.fbsd@quip.cz> wrote: > > > > 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 > > I believe the first number is the objset number, where the objset can > be either a dataset or a snapshot. The corrupt block likely exists in > multiple snapshots, but "zpool status" will show only one, whichever > it happened to find first. You can see the objset numbers for > datasets (but not snapshots) in the output of "sysctl kstat.zfs". The > second number I believe is the object number, and that should never > change. > --00000000000043b10605ccde6151--