From owner-freebsd-stable@freebsd.org  Mon Feb 22 15:13:49 2021
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@mailman.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.nyi.freebsd.org (Postfix) with ESMTP id BEB73541C14
 for <freebsd-stable@mailman.nyi.freebsd.org>;
 Mon, 22 Feb 2021 15:13:49 +0000 (UTC) (envelope-from avg@FreeBSD.org)
Received: from relay1-d.mail.gandi.net (relay1-d.mail.gandi.net
 [217.70.183.193])
 (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 4Dkm0s3jC1z3mV2
 for <freebsd-stable@freebsd.org>; Mon, 22 Feb 2021 15:13:49 +0000 (UTC)
 (envelope-from avg@FreeBSD.org)
X-Originating-IP: 195.64.148.76
Received: from [192.168.0.88] (unknown [195.64.148.76])
 (Authenticated sender: andriy.gapon@uabsd.com)
 by relay1-d.mail.gandi.net (Postfix) with ESMTPSA id 9BA4E240004;
 Mon, 22 Feb 2021 15:13:45 +0000 (UTC)
Subject: Re: lots of "no such file or directory" errors in zfs filesystem
To: Chris Anderson <cva@pobox.com>
Cc: freebsd-stable@freebsd.org
References: <CADuGiuPo2nMtGs=p5FM6H0kQwdXvfTYYrxaiYSC0rjDNo_eBgA@mail.gmail.com>
 <48b78acb-7667-7829-8dd0-e753b7ac3336@FreeBSD.org>
 <CADuGiuPaxLHN3zqR+LrEZ2E9r=cjqS7KhV_LDAHN_wK2fJ-+tw@mail.gmail.com>
From: Andriy Gapon <avg@FreeBSD.org>
Message-ID: <ce5e5114-2640-bbb9-bfaa-ea148afb403d@FreeBSD.org>
Date: Mon, 22 Feb 2021 17:13:44 +0200
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101
 Firefox/78.0 Thunderbird/78.7.1
MIME-Version: 1.0
In-Reply-To: <CADuGiuPaxLHN3zqR+LrEZ2E9r=cjqS7KhV_LDAHN_wK2fJ-+tw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Rspamd-Queue-Id: 4Dkm0s3jC1z3mV2
X-Spamd-Bar: ----
Authentication-Results: mx1.freebsd.org;
	none
X-Spamd-Result: default: False [-4.00 / 15.00];
	 REPLY(-4.00)[]
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Feb 2021 15:13:49 -0000

On 22/02/2021 16:20, Chris Anderson wrote:
> On Mon, Feb 22, 2021 at 1:36 AM Andriy Gapon <avg@freebsd.org
> <mailto:avg@freebsd.org>> wrote:
> 
>     On 22/02/2021 09:31, Chris Anderson wrote:
>     > None of these files are especially important to me, however I was wondering
>     > if there would be any benefit to the community from trying to debug this
>     > issue further to understand what might be going wrong.
> 
>     Yes.
> 
> 
> Could you offer any guidance about what kind of debugging information I could
> collect that would be of use?

You can start with picking a single file that demonstrates the problem.
Then,
ls -li the-file
zdb -dddd file's-filesystem file's-inode-number
The filesystem can be found out from df output, the inode number is in ls -li
output -- if the command prints anything at all.
If it does not, then do ls -lid on the file's directory and then zdb -dddd for
the directory's inode number.  In the output there should be the file name and
its number (I think that it's in hex, but not sure).


-- 
Andriy Gapon