Date: Mon, 22 Feb 2021 17:13:44 +0200 From: Andriy Gapon <avg@FreeBSD.org> To: Chris Anderson <cva@pobox.com> Cc: freebsd-stable@freebsd.org Subject: Re: lots of "no such file or directory" errors in zfs filesystem Message-ID: <ce5e5114-2640-bbb9-bfaa-ea148afb403d@FreeBSD.org> In-Reply-To: <CADuGiuPaxLHN3zqR%2BLrEZ2E9r=cjqS7KhV_LDAHN_wK2fJ-%2Btw@mail.gmail.com> References: <CADuGiuPo2nMtGs=p5FM6H0kQwdXvfTYYrxaiYSC0rjDNo_eBgA@mail.gmail.com> <48b78acb-7667-7829-8dd0-e753b7ac3336@FreeBSD.org> <CADuGiuPaxLHN3zqR%2BLrEZ2E9r=cjqS7KhV_LDAHN_wK2fJ-%2Btw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ce5e5114-2640-bbb9-bfaa-ea148afb403d>