Must copy file from wsl drive to windows drive in order to open and read it.

[pbedenbaugh]

Windows Version

Microsoft Windows [Version 10.0.19045.4957]

WSL Version

WSL version: 2.0.15.0 Kernel version: 5.15.133.1-1 WSLg version: 1.0.59 MSRDC version: 1.2.4677 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.19045.4957

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

Linux version 5.15.133.1-microsoft-standard-WSL2 (root@1c602f52c2e4) (gcc (GCC) 11.2.0, GNU ld (GNU Binutils) 2.37) #1 SMP Thu Oct 5 21:02:42 UTC 2023

Distro Version

Ubunto 22.04

Other Software

Paraview 5.13.1

Repro Steps

open paraview. attempt to open a mesh file from the wsl drive, for example, directory \wsl.localhost\smeca\home\user\NoHook4 file Mesh_1.cgns results in a file open error, and opens and empty object in paraview.
Copy the file to directory C:\Users\REDACTED\femTests\NoHookE, and the file opens fine.

Expected Behavior

good result:

Actual Behavior

bad result:

Diagnostic Logs

ERROR: In vtkIOSSReaderInternal.cxx, line 328
vtkIOSSReader (000001CA6579A960): Error in UpdateTimeInformation:
ERROR: Unable to open CGNS database '//wsl.localhost/smeca/home/user/NoHook4/Mesh_1.cgns' for read access.
[0] CGNS Error: 'cgio_open_file:File-open error'

ERROR: In vtkExecutive.cxx, line 730
vtkPVCompositeDataPipeline (000001CA6E903D60): Algorithm vtkIOSSReader (000001CA6579A960) returned failure for request: vtkInformation (000001CA6FF0FB20)
Debug: Off
Modified Time: 1701561
Reference Count: 1
Registered Events: (none)
Request: REQUEST_INFORMATION
FORWARD_DIRECTION: 0
ALGORITHM_AFTER_FORWARD: 1

ERROR: In vtkExecutive.cxx, line 730
vtkPVCompositeDataPipeline (000001CA6E903D60): Algorithm vtkIOSSReader (000001CA6579A960) returned failure for request: vtkInformation (000001CA6D9F01B0)
Debug: Off
Modified Time: 1704450
Reference Count: 1
Registered Events: (none)
Request: REQUEST_DATA
FORWARD_DIRECTION: 0
ALGORITHM_AFTER_FORWARD: 1
FROM_OUTPUT_PORT: 0

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

[pbedenbaugh]

Mesh_1.zip
This is an example file.

[github-actions]

Failed to parse logs. Unexpected file: Mesh_1.cgns
The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information

Found no WSL traces in the logs

[pbedenbaugh]

C:\Users\Purvis\WslLogs-2024-10-04_10-24-03.zip