From nobody Tue Nov 29 08:55:04 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 4NLx4M3gxVz4jGkW for ; Tue, 29 Nov 2022 08:55:15 +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 4NLx4M1t0jz3kwx for ; Tue, 29 Nov 2022 08:55:15 +0000 (UTC) (envelope-from ml@netfence.it) Authentication-Results: mx1.freebsd.org; none 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 2AT8t4uu060090 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Tue, 29 Nov 2022 09:55:04 +0100 (CET) (envelope-from ml@netfence.it) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netfence.it; s=202210; t=1669712104; bh=3amKc61c4/KzHm8RKZKlJpWfjO444TCSpDjge7BeBt8=; h=Date:Subject:To:References:Cc:From:In-Reply-To; b=ujimO2Unl7JukQfZNzvnUUBMYYewOyZh7KInObTmxX79X6xPMh8CV9sDukVgIdzwl d5+dPqYZBiPOnI3H9xkxy/dbzoO9UjtQkK3tFFM5QFOvODODgm4pcY+0xartGs7J7t BnUXMg2IQBi1CWlWJ/xSg9/2Yq19JVYllVRFJ16A= X-Authentication-Warning: soth.netfence.it: Host alamar.local.netfence.it [10.1.2.18] claimed to be [10.1.2.18] Message-ID: <47265e09-3aa0-24fa-22cb-56e09bb524f0@netfence.it> Date: Tue, 29 Nov 2022 09:55:04 +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 References: <0ddaa537-ffa9-af0d-1a5a-1874a67ed2b5@netfence.it> <5def1695-82b3-3441-c11a-d64ca0c7c30a@netfence.it> <255658040.26515.1669699637761@orville.co-bxl> Cc: questions@freebsd.org From: Andrea Venturoli In-Reply-To: <255658040.26515.1669699637761@orville.co-bxl> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4NLx4M1t0jz3kwx X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:35612, ipnet:78.134.0.0/17, country:IT] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On 11/29/22 06:27, Sysadmin Lists wrote: Hello! > The construct is :. It looks like you deleted the dataset > the corrupted file was found on, so now ZFS displays it as that string. This is useful info. Could the meaning of "dataset" include snapshots too? I don't think I deleted a dataset, but I've got automatical periodical snapshotting (of course deleting old ones). Scratching my head here... If I had a corrupted file on a dataset: first, why was it not detected earlier? Second, if I delete that dataset, why didn't the (corrupted) file go away with it? (If a dataset does not exist anymore, how can it still have files?) > You can check `zpool history' for what it was called. Unfortunately, it's quite hard: # zpool history zroo2 | grep "2022-11-2[56].*destroy"|wc 802 3229 61694 > Bottom of the page here: > https://docs.oracle.com/cd/E19253-01/819-5461/gbctx/index.html Sorry, but I don't get it. Unless I'm missing something, it describes what to do when a file (or its metadata) is corrupted; you say the corrupted file was on a destroyed dataset. So I do I "move" or "delete" it now, if I cannot address it??? bye & Thanks av.