Checks
Describe the bug you encountered:
When --show-errors is passed and encountering a file that seems to be corrupted, fd will endlessly spam [fd error]: Input/output error (os error 5) to stderr and fail to ever terminate or to scan further files. I've encountered this numerous times recently, and when stderr is redirected to a file, fd will fill up the entire disk with that same line - one incident the file grew to 60 gigabytes before I terminated fd, and the entire file (as checked with uniq -c) consisted of just that one line repeated millions of times.
Describe what you expected to happen:
fd to report the error reading that file once (including the name of the file), and skip it and continue on gracefully
What version of fd are you using?
fd 8.5.3
Which operating system / distribution are you on?
Linux 6.0.9-arch1-1 x86_64
LSB Version: n/a
Distributor ID: Arch
Description: Arch Linux
Release: rolling
Codename: n/a
Checks
Describe the bug you encountered:
When
--show-errorsis passed and encountering a file that seems to be corrupted, fd will endlessly spam[fd error]: Input/output error (os error 5)to stderr and fail to ever terminate or to scan further files. I've encountered this numerous times recently, and when stderr is redirected to a file, fd will fill up the entire disk with that same line - one incident the file grew to 60 gigabytes before I terminated fd, and the entire file (as checked withuniq -c) consisted of just that one line repeated millions of times.Describe what you expected to happen:
fd to report the error reading that file once (including the name of the file), and skip it and continue on gracefully
What version of
fdare you using?fd 8.5.3
Which operating system / distribution are you on?