URL: <https://savannah.gnu.org/bugs/?68223>
Summary: recent macOS: find / - failed to read file names
from file system at or below ‘/’
Group: findutils
Submitter: raf
Submitted: Fri 10 Apr 2026 01:44:00 AM UTC
Category: None
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: None
Status: None
Privacy: Public
Assigned to: None
Originator Name:
Originator Email:
Open/Closed: Open
Discussion Lock: Unlocked
Release: None
Fixed Release: None
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: Fri 10 Apr 2026 01:44:00 AM UTC By: raf <raf>
gfind (GNU findutils) 4.10.0 (via macports)
M1 MacStudio, macOS-14.6
command (as root):
gfind / >gfind.out
On the above system with about 6 million files, gfind stopped after about a
million with this error:
gfind: failed to read file names from file system at or below ‘/’: No
such file or directory
It doesn't happen on my old macOS system (macOS-10.14).
I expected it to list all the file system entries on the system, and to emit
non-fatal errors.
It doesn't seem to have anything to do with SIP, because the version of find
that comes with the mac is also affected by SIP and doesn't have this
problem.
I searched for the error message and found this from 4 years ago (relating to
macOS-11.6):
https://superuser.com/questions/1679798/gnu-find-error-find-failed-to-read-file-names-from-file-system-at-or-below
There are other references to it in relation to MSYS2 on windows with non-NTFS
file systems.
I saw a comment that it only happens when searching / itself.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?68223>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
