All file enumerations methods fail with System.IO.IOException: 'An unexpected network error occurred' when enumerating large network foler structures
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- csharp
- Domain
- networking, operating-systems
Research direction
Start by reproducing the failure through Directory.GetFiles with the shown EnumerationOptions against the large Synology SMB3 structure, then compare it with the other file-enumeration methods named in the report. Trace the relevant System.IO enumeration entry points and establish why network enumeration fails after about five minutes; done means the same structure enumerates successfully without the reported IOException.
Written by the indexing model from the issue text.
Description
Description
Enumeration fails when using any of the file enumeration methods such as File.IO.GetFiles, EnumerateFiles, EnumerateFileSystemEntries or DirectoryInfo.... on large network structures.
x86 and x64 debug in VS, running against a Synology NAS using SMB3 on a local network - folder has about 1.2 million files in 60k folders.
Reproduction Steps
EnumerationOptions enumerationOptions = new() { BufferSize = 65535, IgnoreInaccessible = true, RecurseSubdirectories = true, AttributesToSkip = FileAttributes.Device };
var files = Directory.GetFiles(testPath, "*", enumerationOptions);
Expected behavior
It should be able to enumerate the files - It works fine on the same file structure for SSD and HDD, just not over the network.
Actual behavior
After about 5 minutes, all enumeration methods fail with System.IO.IOException: 'An unexpected network error occurred'
Regression?
Error is on .net 6,7,8,9
Known Workarounds
Enumerate folder by folder via recursion in code
Configuration
.Net 9
Windows 11 23H2 x64
Issue is the same from a Windows 10 test machine
Other information
No response
- Dominant language
- C#
- Stars
- 18.3k
- Forks
- 5.6k
- PR merge metrics
- PR metrics pending
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dotnet/runtime
-
agentic-workflows untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
area-System.Reflection blocking-clean-ci-optional Known Build Error os-mac-os-x untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
area-CodeGen-coreclr untriaged
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
agentic-workflows untriaged
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
area-VM-meta-mono untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
:watch: Not Triaged 11.0 fundamentals/subsvc
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
dotnet/AspNetCore.Docs#37699 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SubtitleEdit/subtitleedit#15108 · 1 comment ·
-
area/docs-content Bug pulumi/docs
Difficulty 1/5 1-3 hours Newbie friendliness 94/100
-
Create parent directories only after the containment check in InstallHelper.TryExtractToDirectory Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PowerShell/PSResourceGet#2056 ·