Skip to content

"find" erroring after network data migration to NetApp FAS2620. #1497

Description

@thomasmansencal
  • 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?

2.13.0 64bit and 2.16.1.4 64bit

$ git --version --build-options
git version 2.13.0.windows.1
built from commit: eba7af3dbb4c846c6303c5f64102acee696c9ab0
sizeof-long: 4
machine: x86_64
  • 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.15063]
  • What options did you set as part of the installation? Or did you choose the
    defaults?
# One of the following:
> type "C:\Program Files\Git\etc\install-options.txt"
> type "C:\Program Files (x86)\Git\etc\install-options.txt"
> type "%USERPROFILE%\AppData\Local\Programs\Git\etc\install-options.txt"
$ cat /etc/install-options.txt

Does not apply: We are running from a shared network installation.
  • Any other interesting things about your environment that might be related
    to the issue you're seeing?

We have recently migrated our data over a CIFS share from on a NetApp FAS2620 running Cluster Mode Release 9.2.

Details

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

Bash and CMD

thomas@MORGOTH MINGW64 /T/Level_0
$ find .
.
./Level_1a
./Level_1a/Level_2
./Level_1a/Level_2/Level_3
./Level_1a/Level_2/Level_3/Level_4
./Level_1a/Level_2/Level_3/Level_4/Level_5
./Level_1a/Level_2/Level_3/Level_4/Level_5/john.txt
./Level_1b
./Level_1b/Level_2
./Level_1b/Level_2/Level_3
./Level_1b/Level_2/Level_3/Level_4
./Level_1b/Level_2/Level_3/Level_4/Level_5
./Level_1b/Level_2/Level_3/Level_4/Level_5/Level_6
./Level_1b/Level_2/Level_3/Level_4/Level_5/Level_6/john.txt
find: failed to read file names from file system at or below '.': No such file or directory
  • What did you expect to occur after running these commands?

find should not raise any errors.

  • What actually happened instead?

find errors and stops:

find: failed to read file names from file system at or below '.': No such file or directory

We also have Cygwin deployed similarly and shared from the network and its find command is successful:

thomas@MORGOTH /cygdrive/t/Level_0
$ find .
.
./Level_1a
./Level_1a/Level_2
./Level_1a/Level_2/Level_3
./Level_1a/Level_2/Level_3/Level_4
./Level_1a/Level_2/Level_3/Level_4/Level_5
./Level_1a/Level_2/Level_3/Level_4/Level_5/john.txt
./Level_1b
./Level_1b/Level_2
./Level_1b/Level_2/Level_3
./Level_1b/Level_2/Level_3/Level_4
./Level_1b/Level_2/Level_3/Level_4/Level_5
./Level_1b/Level_2/Level_3/Level_4/Level_5/Level_6
./Level_1b/Level_2/Level_3/Level_4/Level_5/Level_6/john.txt
./Level_1c
./Level_1c/Level_2
./Level_1c/Level_2/Level_3
./Level_1c/Level_2/Level_3/Level_4
./Level_1c/Level_2/Level_3/Level_4/Level_5
./Level_1c/Level_2/Level_3/Level_4/Level_5/Level_6
./Level_1c/Level_2/Level_3/Level_4/Level_5/Level_6/Level_7
./Level_1c/Level_2/Level_3/Level_4/Level_5/Level_6/Level_7/john.txt

Something we noticed after hours of testing around the problem is that it seems to be related to nesting directories level, anything above 5 will cause git bash find to error.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions