• I was not able to find an open or closed issue matching what I'm seeing

Setup

• Which version of Git for Windows are you using? Is it 32-bit or 64-bit?

$ git --version --build-options

git version 2.16.2.windows.1
cpu: x86_64
built from commit: e1848984d1004040ec5199e749b5f282ddf4bb09
sizeof-long: 4

• Which version of Windows are you running? Vista, 7, 8, 10? Is it 32-bit or 64-bit?

$ cmd.exe /c ver

Microsoft Windows [Version 10.0.16299.248]

• What options did you set as part of the installation? Or did you choose the
  defaults?

$ cat /etc/install-options.txt

Editor Option: VIM
Path Option: Cmd
SSH Option: OpenSSH
CURL Option: OpenSSL
CRLF Option: CRLFCommitAsIs
Bash Terminal Option: MinTTY
Performance Tweaks FSCache: Enabled
Use Credential Manager: Enabled
Enable Symlinks: Enabled

• Any other interesting things about your environment that might be related
  to the issue you're seeing?

Only happens when I manipulate directories on a driver with exFAT file system (512 bytes/sector, 8 sectors/cluster, 4KB/cluster)

Details

• Which terminal/shell are you running Git from? e.g Bash/CMD/PowerShell/other

Bash

• What commands did you run to trigger this issue?

$ mkdir -p f1/f2/f3/f4/f5/f6 && touch f1/f2/f3/f4/f5/f6/foo.bar
$ rm -rf f1

• What did you expect to occur after running these commands?

Everything will be fine if max relative folder depth <= 5 (not absolute path depth).
Any command recursively does something to a folder contains more than 5 levels (like chmod -R) will raise the error fts_read failed: No such file or directory and stop, although the files inside that folder have been removed.

• What actually happened instead?

rm: fts_read failed: No such file or directory