# Can read wsl2 rmed file only after copying to windows directory

**URL:** https://discourse.paraview.org/t/can-read-wsl2-rmed-file-only-after-copying-to-windows-directory/15480
**Category:** ParaView Support
**Created:** [October 1, 2024, 5:09pm UTC](https://discourse.paraview.org/t/can-read-wsl2-rmed-file-only-after-copying-to-windows-directory/15480 "2024-10-01T17:09:44Z")
**Posts on this page:** 12
**Page:** 1

<div class="post-metadata">

### Author: ![phb](https://discourse.paraview.org/user_avatar/discourse.paraview.org/phb/32/3663_2.png) [@phb](https://discourse.paraview.org/u/phb)
#### Post date: [October 1, 2024, 5:09pm UTC](https://discourse.paraview.org/t/can-read-wsl2-rmed-file-only-after-copying-to-windows-directory/15480/1 "2024-10-01T17:09:44Z")

</div>

Paraview 5.13.1, Windows 10

Directly opening a .rmed file created on wsl2 fails with errors.  
Example path \wsl.localhost\smeca\home\user\NoHook3\NoHook\_StudyD\_NL.rmed

The file opens fine after copying to a directory on the windows C: drive

Installing paraview directly on wsl2 failed because of libxcb problems.  
Windows paraview work great so far, but it would certainly be more convenient to not have to copy the files from wsl to the c: drive. Is there a workaround to enable that workflow ?  
Thank you.

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [October 2, 2024, 7:29am UTC](https://discourse.paraview.org/t/can-read-wsl2-rmed-file-only-after-copying-to-windows-directory/15480/2 "2024-10-02T07:29:19Z")

</div>

What error do you have ?

Are you able to open other formats ?

---

<div class="post-metadata">

### Author: ![phb](https://discourse.paraview.org/user_avatar/discourse.paraview.org/phb/32/3663_2.png) [@phb](https://discourse.paraview.org/u/phb)
#### Post date: [October 2, 2024, 3:43pm UTC](https://discourse.paraview.org/t/can-read-wsl2-rmed-file-only-after-copying-to-windows-directory/15480/3 "2024-10-02T15:43:13Z")

</div>

```auto
ERROR: In vtkQuadraturePointsGenerator.cxx, line 220
vtkMEDQuadraturePointsGenerator (000002BB0A7CDC20): configuration error

ERROR: In vtkMEDQuadraturePointsGenerator.cxx, line 73
vtkMEDQuadraturePointsGenerator (000002BB0A7CDC20): Filter data has not been configured correctly. Aborting.

ERROR: In vtkQuadraturePointsGenerator.cxx, line 220
vtkMEDQuadraturePointsGenerator (000002BB0A7CDC20): configuration error

ERROR: In vtkMEDQuadraturePointsGenerator.cxx, line 73
vtkMEDQuadraturePointsGenerator (000002BB0A7CDC20): Filter data has not been configured correctly. Aborting.

Generic Warning: In vtkSMColorMapEditorHelper.cxx, line 706
Could not determine array range.

Exception has been thrown in vtkMEDReader::RequestInformation : File : "\\wsl.localhost\smeca\home\user\NoHook4\NoHookStudyE_Lin.rmed" has been detected as unreadable by MED file : impossible to read anything !
ERROR: In vtkExecutive.cxx, line 730
vtkPVCompositeDataPipeline (000002BB088C4ED0): Algorithm vtkFileSeriesGroupReader (000002BB0BB21E00) returned failure for request: vtkInformation (000002BB76294C30)
  Debug: Off
  Modified Time: 42856391
  Reference Count: 1
  Registered Events: (none)
  Request: REQUEST_INFORMATION
  FORWARD_DIRECTION: 0
  ALGORITHM_AFTER_FORWARD: 1

Exception has been thrown in vtkMEDReader::RequestInformation : File : "\\wsl.localhost\smeca\home\user\NoHook4\NoHookStudyE_Lin.rmed" has been detected as unreadable by MED file : impossible to read anything !
ERROR: In vtkExecutive.cxx, line 730
vtkPVCompositeDataPipeline (000002BB088C3BB0): Algorithm vtkMEDReader (000002BB088C33D0) returned failure for request: vtkInformation (000002BB76296980)
  Debug: Off
  Modified Time: 42856422
  Reference Count: 1
  Registered Events: (none)
  Request: REQUEST_INFORMATION
  FORWARD_DIRECTION: 0
  ALGORITHM_AFTER_FORWARD: 1

```

---

<div class="post-metadata">

### Author: ![phb](https://discourse.paraview.org/user_avatar/discourse.paraview.org/phb/32/3663_2.png) [@phb](https://discourse.paraview.org/u/phb)
#### Post date: [October 2, 2024, 3:47pm UTC](https://discourse.paraview.org/t/can-read-wsl2-rmed-file-only-after-copying-to-windows-directory/15480/4 "2024-10-02T15:47:39Z")

</div>

I have not tried other formats. I’m getting started with salome-mecam, and am generating lots of rmed files at the moment. The embedded paraview within salome-meca is less performant, and also goes through periods of frequent segmentation faults. So far so good with the windows version.

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [October 2, 2024, 3:48pm UTC](https://discourse.paraview.org/t/can-read-wsl2-rmed-file-only-after-copying-to-windows-directory/15480/5 "2024-10-02T15:48:50Z")

</div>

> [@phb](#):
>
> I have not tried other formats.

Please check if this is a .med specific issue or present with any format.

---

<div class="post-metadata">

### Author: ![phb](https://discourse.paraview.org/user_avatar/discourse.paraview.org/phb/32/3663_2.png) [@phb](https://discourse.paraview.org/u/phb)
#### Post date: [October 2, 2024, 4:29pm UTC](https://discourse.paraview.org/t/can-read-wsl2-rmed-file-only-after-copying-to-windows-directory/15480/6 "2024-10-02T16:29:09Z")

</div>

Opening from directory C:\Users\REDACTED\femTests\NoHookE file Mesh\_1.cgns works fine, using the CGNS Series Reader.

Opening from directory \wsl.localhost\smeca\home\user\NoHook4 file Mesh\_1.cgns generates the errors:

```auto
ERROR: In vtkIOSSReaderInternal.cxx, line 328
vtkIOSSReader (000002BB059199E0): 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 (000002BB722D6980): Algorithm vtkIOSSReader (000002BB059199E0) returned failure for request: vtkInformation (000002BB0C618F90)
  Debug: Off
  Modified Time: 44649853
  Reference Count: 1
  Registered Events: (none)
  Request: REQUEST_INFORMATION
  FORWARD_DIRECTION: 0
  ALGORITHM_AFTER_FORWARD: 1

ERROR: In vtkExecutive.cxx, line 730
vtkPVCompositeDataPipeline (000002BB722D6980): Algorithm vtkIOSSReader (000002BB059199E0) returned failure for request: vtkInformation (000002BB7606FAF0)
  Debug: Off
  Modified Time: 44653132
  Reference Count: 1
  Registered Events: (none)
  Request: REQUEST_DATA
  FORWARD_DIRECTION: 0
  ALGORITHM_AFTER_FORWARD: 1
  FROM_OUTPUT_PORT: 0

```

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [October 3, 2024, 7:24am UTC](https://discourse.paraview.org/t/can-read-wsl2-rmed-file-only-after-copying-to-windows-directory/15480/7 "2024-10-03T07:24:55Z")

</div>

Looks like there is an issue with the way Windows “mount” wsl folders. Can you navigate to the folder in the windows explorer ? Which path is displayed in that case ?

---

<div class="post-metadata">

### Author: ![phb](https://discourse.paraview.org/user_avatar/discourse.paraview.org/phb/32/3663_2.png) [@phb](https://discourse.paraview.org/u/phb)
#### Post date: [October 3, 2024, 1:39pm UTC](https://discourse.paraview.org/t/can-read-wsl2-rmed-file-only-after-copying-to-windows-directory/15480/8 "2024-10-03T13:39:40Z")

</div>

Yes, of course - the path to the directory is \wsl.localhost\smeca\home\user\NoHook4

That is from copy-paste from the navication bar.  
It displays differently, as shown in the screen shot

 ![image](https://discourse.paraview.org/uploads/default/original/2X/0/020d494f5131e4b002fc1eb7bdd09e445f526886.png)

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [October 3, 2024, 1:55pm UTC](https://discourse.paraview.org/t/can-read-wsl2-rmed-file-only-after-copying-to-windows-directory/15480/9 "2024-10-03T13:55:34Z")

</div>

This issues is here: [https://gitlab.kitware.com/paraview/paraview/-/issues/21476](https://gitlab.kitware.com/paraview/paraview/-/issues/21476)

No fixes yet I’m afraid.

---

<div class="post-metadata">

### Author: ![phb](https://discourse.paraview.org/user_avatar/discourse.paraview.org/phb/32/3663_2.png) [@phb](https://discourse.paraview.org/u/phb)
#### Post date: [October 3, 2024, 2:17pm UTC](https://discourse.paraview.org/t/can-read-wsl2-rmed-file-only-after-copying-to-windows-directory/15480/10 "2024-10-03T14:17:47Z")

</div>

Thank you. It seems different from the description in the issue, because paraview does not crash or freeze - it simply opens the file as an empyt vtk data set collection. 0 cells, 0 points … 0 memory. The empty stub can be delted with out apparent consequence.

---

<div class="post-metadata">

### Author: ![Michael\_Li](https://discourse.paraview.org/user_avatar/discourse.paraview.org/michael_li/32/13976_2.png) [@Michael\_Li](https://discourse.paraview.org/u/Michael_Li)
#### Post date: [October 3, 2024, 9:23pm UTC](https://discourse.paraview.org/t/can-read-wsl2-rmed-file-only-after-copying-to-windows-directory/15480/11 "2024-10-03T21:23:40Z")

</div>

I have a similar issue when opening **samrai** file from WSL Ubuntu. It works fine by copying it from WSL2 to Windows.

No matter using a mapped drive or the UNC path like **\wsl.localhost.…**

```auto
ERROR: In vtkVisItSAMRAIReader.cxx, line 135
vtkVisItSAMRAIReader (00000288DC0B4CF0): There was an error opening Z:\home\michael\simulation\ibamr-run\BScompisite\ibfe-ex4-tracer\viz_IB2d\visit_dump.00000\summary.samrai. It may be an invalid file.

ERROR: In vtkExecutive.cxx, line 730
vtkPVCompositeDataPipeline (00000288DC8E2B10): Algorithm vtkFileSeriesReader (00000288DB853950) returned failure for request: vtkInformation (00000288BC601260)
  Debug: Off
  Modified Time: 430674
  Reference Count: 1
  Registered Events: (none)
  Request: REQUEST_DATA_OBJECT
  FORWARD_DIRECTION: 0
  ALGORITHM_AFTER_FORWARD: 1

ERROR: In vtkAvtSTMDFileFormatAlgorithm.cxx, line 127
vtkVisItSAMRAIReader (00000288DC0B4CF0): Unable to find any meshes

ERROR: In vtkExecutive.cxx, line 730
vtkPVCompositeDataPipeline (00000288DC8E2B10): Algorithm vtkFileSeriesReader (00000288DB853950) returned failure for request: vtkInformation (00000288BC601260)
  Debug: Off
  Modified Time: 430674
  Reference Count: 1
  Registered Events: (none)
  Request: REQUEST_DATA_OBJECT
  FORWARD_DIRECTION: 0
  ALGORITHM_AFTER_FORWARD: 1

ERROR: In vtkAvtSTMDFileFormatAlgorithm.cxx, line 127
vtkVisItSAMRAIReader (00000288DC0B4CF0): Unable to find any meshes

ERROR: In vtkExecutive.cxx, line 730
vtkPVCompositeDataPipeline (00000288DC8E2B10): Algorithm vtkFileSeriesReader (00000288DB853950) returned failure for request: vtkInformation (00000288BC601260)
  Debug: Off
  Modified Time: 430674
  Reference Count: 1
  Registered Events: (none)
  Request: REQUEST_DATA_OBJECT
  FORWARD_DIRECTION: 0
  ALGORITHM_AFTER_FORWARD: 1

```

---

<div class="post-metadata">

### Author: ![phb](https://discourse.paraview.org/user_avatar/discourse.paraview.org/phb/32/3663_2.png) [@phb](https://discourse.paraview.org/u/phb)
#### Post date: [October 4, 2024, 2:29pm UTC](https://discourse.paraview.org/t/can-read-wsl2-rmed-file-only-after-copying-to-windows-directory/15480/12 "2024-10-04T14:29:10Z")

</div>

I opened an issue for wsl:

> <https://github.com/microsoft/WSL/issues/12128>
>
> \### Windows Version
> 
> Microsoft Windows \[Version 10.0.19045.4957\]
> 
> \### WSL Versio…n
> 
> 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?
> 
> \- \[X\] 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: 
> !\[image\](https://github.com/user-attachments/assets/4049cb61-9e18-4105-875b-14cb3454561b)
> 
> 
> 
> \### Actual Behavior
> 
> bad result:
> !\[image\](https://github.com/user-attachments/assets/8ceef44e-c93a-45e4-90a8-a9f0fc68d9a8)
> 
> \### 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