From nobody Thu Dec 01 15:50:09 2022 X-Original-To: questions@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 4NNLBM5sRCz4jXKL for ; Thu, 1 Dec 2022 15:50:19 +0000 (UTC) (envelope-from ml@netfence.it) Received: from soth.netfence.it (mailserver.netfence.it [78.134.96.152]) (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 (2048 bits) client-digest SHA256) (Client CN "mailserver.netfence.it", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4NNLBL2Zjcz4FPS for ; Thu, 1 Dec 2022 15:50:18 +0000 (UTC) (envelope-from ml@netfence.it) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=netfence.it header.s=202210 header.b=L6fXKr8w; spf=pass (mx1.freebsd.org: domain of ml@netfence.it designates 78.134.96.152 as permitted sender) smtp.mailfrom=ml@netfence.it; dmarc=pass (policy=none) header.from=netfence.it Received: from [10.1.2.18] (alamar.local.netfence.it [10.1.2.18]) (authenticated bits=0) by soth.netfence.it (8.17.1/8.17.1) with ESMTPSA id 2B1Fo9oE096061 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Thu, 1 Dec 2022 16:50:09 +0100 (CET) (envelope-from ml@netfence.it) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netfence.it; s=202210; t=1669909809; bh=sj/pA5Xc1UzvdAMJtD4ya7O0M75ag8Jdw50nmo+AqGw=; h=Date:Subject:To:References:Cc:From:In-Reply-To; b=L6fXKr8w/a5of9eFYckgXY10YIdaoyNjxmEFEW7EbxeVv/21T7pvov599eLRKmchh e943vBo5v3adDcHlL3HXix1X0Q6kCvADhjU2tDvrJShtD/+op2/AsnynzwUhwW65OT Z6dYYDD98tlh89ozvDs+psFl3dZPlsW0dbUTDU+0= X-Authentication-Warning: soth.netfence.it: Host alamar.local.netfence.it [10.1.2.18] claimed to be [10.1.2.18] Message-ID: <2d897f57-5bdc-7497-d374-e7a536d9a440@netfence.it> Date: Thu, 1 Dec 2022 16:50:09 +0100 List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.5.0 Subject: Re: ZFS Permanent error <0xffffffffffffffff>:<0x0> Content-Language: en-US To: sysadmin.lists@mailfence.com References: <0ddaa537-ffa9-af0d-1a5a-1874a67ed2b5@netfence.it> <5def1695-82b3-3441-c11a-d64ca0c7c30a@netfence.it> <255658040.26515.1669699637761@orville.co-bxl> <47265e09-3aa0-24fa-22cb-56e09bb524f0@netfence.it> <597333482.1125294.1669791240602@ichabod.co-bxl> Cc: questions@freebsd.org From: Andrea Venturoli In-Reply-To: <597333482.1125294.1669791240602@ichabod.co-bxl> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-4.00 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; DMARC_POLICY_ALLOW(-0.50)[netfence.it,none]; R_DKIM_ALLOW(-0.20)[netfence.it:s=202210]; R_SPF_ALLOW(-0.20)[+ip4:78.134.96.152]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[questions@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:35612, ipnet:78.134.0.0/17, country:IT]; RCPT_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; DKIM_TRACE(0.00)[netfence.it:+]; FROM_HAS_DN(0.00)[]; TO_DN_NONE(0.00)[]; HAS_XAW(0.00)[]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4NNLBL2Zjcz4FPS X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N On 11/30/22 07:54, Sysadmin Lists wrote: > IIRC, snapshots are valid entries. Perhaps the corrupted file is still > associated with other snapshots. You might need to use `zdb' to find it and > delete it from the filesystem Thanks for your explanation, but this is beyond my skills currently (i.e. unless I find a good tutorial on zdb). What should I be looking for? If the file is associated to another snapshot, why doesn't it say the name of this snapshot, instead of the deleted one? In any case, you are saying my storage isn't exploding and I can live with this harmless warning? If it's so, well, maybe it will go away someday as older automatical snapshots are deleted. bye & Thanks av.