From owner-freebsd-stable@freebsd.org Mon Feb 22 07:31:55 2021 Return-Path: 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 6F44354B8BB for ; Mon, 22 Feb 2021 07:31:55 +0000 (UTC) (envelope-from chris.anderson@gmail.com) Received: from mail-wm1-f47.google.com (mail-wm1-f47.google.com [209.85.128.47]) (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 4DkYlt55Scz4kjy for ; Mon, 22 Feb 2021 07:31:54 +0000 (UTC) (envelope-from chris.anderson@gmail.com) Received: by mail-wm1-f47.google.com with SMTP id p3so2366530wmc.2 for ; Sun, 21 Feb 2021 23:31:54 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=pYt2Mi+gRbYVrABMc9B3N5oeNFrSkW+mAZje8z9I8sI=; b=pDWVqRLhksyNNRVv+qrXfQBJFWWjiIe5qrMZgxF1y3DfMGPyqAbyu6hos7pbH+xpo9 R5waeP0tT+ZWXXQq6ayD3bBnyNn4nxrEOQu9FjrYAebLVLezOOq0DiJdf2Bv0Xv7PkC3 eoFnd/rNjsbej5pks0rI3HA3cqLM7E6q5nybSs06N5I29Ffi5nxueG6/H3GdxAWLAC1w AevGRan9YdbN1Or38xmHl5ySrilcy1O/wLRDXN10bz6r58tYVxQYwKX2ZOjsVTYNt2tf zMHFtLy6zxeOAdC1UvHxDKQhkR9NbejcMnA4K6Bz13yVTCUmjjZmC1DWJplXVEyEEfR/ NmUw== X-Gm-Message-State: AOAM5323CJHnthiZebhUMrXV71LuAhxC5mLdVhcymcZMBNY9X+9wsKPO 80HAPMMrRsqKIC9dNzucD9P1rWnIXPP7mws16dR03T2SZ5o= X-Google-Smtp-Source: ABdhPJzKyiLe+xjZ0D15elfiNabp17pDFnlJvYuWcmexE4x9YiquEcq0LQARHNP1Ydnjfk8oejUxVBbA5nSyBAB5Vno= X-Received: by 2002:a05:600c:2155:: with SMTP id v21mr18769315wml.23.1613979112734; Sun, 21 Feb 2021 23:31:52 -0800 (PST) MIME-Version: 1.0 From: Chris Anderson Date: Mon, 22 Feb 2021 01:31:41 -0600 Message-ID: Subject: lots of "no such file or directory" errors in zfs filesystem To: freebsd-stable@freebsd.org X-Rspamd-Queue-Id: 4DkYlt55Scz4kjy X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=pobox.com (policy=none); spf=pass (mx1.freebsd.org: domain of chrisanderson@gmail.com designates 209.85.128.47 as permitted sender) smtp.mailfrom=chrisanderson@gmail.com X-Spamd-Result: default: False [-2.90 / 15.00]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; TO_DN_NONE(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FORGED_SENDER(0.30)[cva@pobox.com,chrisanderson@gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; FROM_NEQ_ENVFROM(0.00)[cva@pobox.com,chrisanderson@gmail.com]; RBL_DBL_DONT_QUERY_IPS(0.00)[209.85.128.47:from]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; TAGGED_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[209.85.128.47:from:127.0.2.255]; RCVD_IN_DNSWL_NONE(0.00)[209.85.128.47:from]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.128.47:from]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-stable]; DMARC_POLICY_SOFTFAIL(0.10)[pobox.com : SPF not aligned (relaxed), No valid DKIM, none] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Feb 2021 07:31:55 -0000 I'm in the process of decommissioning an old zfs based file server and I noticed that around a dozen files with directory entries which fail with "No such file or directory" when trying to read them. I can't remember what the original version of freebsd installed was, but it's been in production for at least 7 years and has been upgraded with freebsd-update as new FreeBSD releases came available (it is currently on 12.2-RELEASE-p3). The behavior is perplexing since I've never had any scrub failures on the pool those files reside in yet from looking at old security run outputs, the number of files in that state has increased over time. 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.