# Error reading large VTK files in the Windows version
**URL:** https://discourse.paraview.org/t/error-reading-large-vtk-files-in-the-windows-version/8199
**Category:** ParaView Support
**Tags:** vtk
**Created:** [October 16, 2021, 6:39am UTC](https://discourse.paraview.org/t/error-reading-large-vtk-files-in-the-windows-version/8199 "2021-10-16T06:39:29Z")
**Posts on this page:** 20
**Page:** 1
### Author:  [@vmajor](https://discourse.paraview.org/u/vmajor)
#### Post date: [October 16, 2021, 6:39am UTC](https://discourse.paraview.org/t/error-reading-large-vtk-files-in-the-windows-version/8199/1 "2021-10-16T06:39:29Z")
I have large (3.5 Gb+) VTK files generated by our CFD software running on Ubuntu (WSL2 in Windows 11 in fact).
Paraview 5.10.0-RC1 running on Ubuntu WSL2 opens the file correctly, albeit the Nvidia virtualised driver tends to crash so I cannot actually use this method. Previously using previous versions of Paraview I successfully worked with the results files in native Ubuntu. The point is that our results files are not corrupted or faulty.
Paraview 5.10.0-RC1 running on Windows 11 while opening the same files reports the errors previously reported by others in other threads:
```auto
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XMLParser\vtkXMLDataParser.cxx, line 655
vtkXMLDataParser (0000021A1A785910): Error reading uncompressed binary data header. Read 0 of 4 bytes.
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XML\vtkXMLStructuredDataReader.cxx, line 345
vtkXMLImageDataReader (0000021A067EEAB0): Error reading extent 1 597 1 309 1 285 from piece 0
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XML\vtkXMLDataReader.cxx, line 410
vtkXMLImageDataReader (0000021A067EEAB0): Cannot read point data array "vorticityNorm" from PointData in piece 0. The data array in the element may be too short.
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XMLParser\vtkXMLDataParser.cxx, line 655
vtkXMLDataParser (0000021A1A785910): Error reading uncompressed binary data header. Read 0 of 4 bytes.
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XML\vtkXMLStructuredDataReader.cxx, line 345
vtkXMLImageDataReader (0000021A067EEAB0): Error reading extent 1 597 1 309 1 285 from piece 0
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XML\vtkXMLDataReader.cxx, line 410
vtkXMLImageDataReader (0000021A067EEAB0): Cannot read point data array "vorticityNorm" from PointData in piece 0. The data array in the element may be too short.
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XMLParser\vtkXMLDataParser.cxx, line 655
vtkXMLDataParser (0000021A1A785910): Error reading uncompressed binary data header. Read 0 of 4 bytes.
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XML\vtkXMLStructuredDataReader.cxx, line 345
vtkXMLImageDataReader (0000021A067EEAB0): Error reading extent 1 597 1 309 1 285 from piece 0
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XML\vtkXMLDataReader.cxx, line 410
vtkXMLImageDataReader (0000021A067EEAB0): Cannot read point data array "vorticityNorm" from PointData in piece 0. The data array in the element may be too short.
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XMLParser\vtkXMLDataParser.cxx, line 655
vtkXMLDataParser (0000021A1A785910): Error reading uncompressed binary data header. Read 0 of 4 bytes.
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XML\vtkXMLStructuredDataReader.cxx, line 345
vtkXMLImageDataReader (0000021A067EEAB0): Error reading extent 1 597 1 309 1 285 from piece 0
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XML\vtkXMLDataReader.cxx, line 410
vtkXMLImageDataReader (0000021A067EEAB0): Cannot read point data array "vorticityNorm" from PointData in piece 0. The data array in the element may be too short.
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XMLParser\vtkXMLDataParser.cxx, line 655
vtkXMLDataParser (0000021A1A785910): Error reading uncompressed binary data header. Read 0 of 4 bytes.
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XML\vtkXMLStructuredDataReader.cxx, line 345
vtkXMLImageDataReader (0000021A067EEAB0): Error reading extent 1 597 1 309 1 285 from piece 0
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XML\vtkXMLDataReader.cxx, line 410
vtkXMLImageDataReader (0000021A067EEAB0): Cannot read point data array "vorticityNorm" from PointData in piece 0. The data array in the element may be too short.
```
Thus, this is a Windows build specific problem. Please advise if this is known, recognised and if there is a solution or a workaround on the way.
---
### Author:  [@vmajor](https://discourse.paraview.org/u/vmajor)
#### Post date: [October 17, 2021, 3:31pm UTC](https://discourse.paraview.org/t/error-reading-large-vtk-files-in-the-windows-version/8199/2 "2021-10-17T15:31:20Z")
Some more information.
Windows version is able to open a 162 Mb VTK file without errors, but as mentioned above it fails with the 3.5 Gb VTK file.
Thus it seems to have some hard coded file size limit where it apparently truncates it to some size that it can handle. This of course does not work.
Linux version running in WSL2 Ubuntu 20.04 on the same workstation has no problems with opening the same files.
---
### Author:  [@todoooo](https://discourse.paraview.org/u/todoooo)
#### Post date: [October 17, 2021, 10:01pm UTC](https://discourse.paraview.org/t/error-reading-large-vtk-files-in-the-windows-version/8199/3 "2021-10-17T22:01:39Z")
Which compilers were used?
---
### Author:  [@vmajor](https://discourse.paraview.org/u/vmajor)
#### Post date: [October 18, 2021, 4:26am UTC](https://discourse.paraview.org/t/error-reading-large-vtk-files-in-the-windows-version/8199/4 "2021-10-18T04:26:28Z")
I do not know. Both versions were downloaded precompiled. Do you think building the Windows version from source would fix this? Which compiler do you suggest?
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [October 18, 2021, 9:14am UTC](https://discourse.paraview.org/t/error-reading-large-vtk-files-in-the-windows-version/8199/5 "2021-10-18T09:14:35Z")
Which format are your partitions ?
---
### Author:  [@vmajor](https://discourse.paraview.org/u/vmajor)
#### Post date: [October 18, 2021, 9:16am UTC](https://discourse.paraview.org/t/error-reading-large-vtk-files-in-the-windows-version/8199/6 "2021-10-18T09:16:29Z")
ext4, but even when I copy the domain file to different ntfs partition the error remains.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [October 18, 2021, 9:19am UTC](https://discourse.paraview.org/t/error-reading-large-vtk-files-in-the-windows-version/8199/7 "2021-10-18T09:19:05Z")
I would put data and ParaView on ntfs partition and check again.
---
### Author:  [@vmajor](https://discourse.paraview.org/u/vmajor)
#### Post date: [October 18, 2021, 9:25am UTC](https://discourse.paraview.org/t/error-reading-large-vtk-files-in-the-windows-version/8199/8 "2021-10-18T09:25:08Z")
OK to explain.
1. Linux ParaView is on ext4.
2. Our native Linux CFD solver is on ext4 and the results directory is on ext4.
3. Linux software and partitions are running and mounted under WSL2 on Windows 11.
4. Windows ParaView is on an ntfs partition on the same Windows 11 machine that is running WSL2
Linux ParaView can read and visualize the results data.
Windows ParaView throws up errors with the large domain file (the 3.5 Gb one) when I try to read it from the ext4, or when I copy this file to an ntfs partition. Both files show the same error reading the file and the result cannot be visualized.
Windows ParaView can read the smaller 162 Mb file both from ext4 and the ntfs partitions.
---
### Author:  [@todoooo](https://discourse.paraview.org/u/todoooo)
#### Post date: [October 18, 2021, 9:44am UTC](https://discourse.paraview.org/t/error-reading-large-vtk-files-in-the-windows-version/8199/9 "2021-10-18T09:44:15Z")
My initial thought, which might be completely erroneous, was that _long_ in Linux is 8 bytes whereas it’s 4 bytes in Windows. Maybe that range is being exceeded.
I was going to suggest compilling with clang for both systems to rule out a compiler difference. But it’s probably faster to scan the code for a _long_ type.
---
### Author:  [@vmajor](https://discourse.paraview.org/u/vmajor)
#### Post date: [October 19, 2021, 4:39am UTC](https://discourse.paraview.org/t/error-reading-large-vtk-files-in-the-windows-version/8199/10 "2021-10-19T04:39:00Z")
Thank you for this. Unfortunately this is beyond my skill level. I am hoping that someone from Kitware would flag this issue and propose a fix.
---
### Author:  [@todoooo](https://discourse.paraview.org/u/todoooo)
#### Post date: [October 19, 2021, 5:23am UTC](https://discourse.paraview.org/t/error-reading-large-vtk-files-in-the-windows-version/8199/11 "2021-10-19T05:23:34Z")
I suggest you raise an issue here [https://gitlab.kitware.com/paraview/paraview/-/issues](https://gitlab.kitware.com/paraview/paraview/-/issues) with a link to the (compressed) 3.5Gb VTK data file which causes the problem.
---
### Author:  [@vmajor](https://discourse.paraview.org/u/vmajor)
#### Post date: [October 19, 2021, 5:34am UTC](https://discourse.paraview.org/t/error-reading-large-vtk-files-in-the-windows-version/8199/12 "2021-10-19T05:34:18Z")
> [@vmajor](#):
>
> OK to explain.
>
> 1. Linux ParaView is on ext4.
> 2. Our native Linux CFD solver is on ext4 and the results directory is on ext4.
> 3. Linux software and partitions are running and mounted under WSL2 on Windows 11.
> 4. Windows ParaView is on an ntfs partition on the same Windows 11 machine that is running WSL2
>
> Linux ParaView can read and visualize the results data.
>
> Windows ParaView throws up errors with the large domain file (the 3.5 Gb one) when I try to read it from the ext4, or when I copy this file to an ntfs partition. Both files show the same error reading the file and the result cannot be visualized.
>
> Windows ParaView can read the smaller 162 Mb file both from ext4 and the ntfs partitions.
Done, thank you for the link. I looked for it on GitHub, not realising they are hosting the code with issues tracking on GitLab.
---
### Author:  [@todoooo](https://discourse.paraview.org/u/todoooo)
#### Post date: [October 19, 2021, 5:37am UTC](https://discourse.paraview.org/t/error-reading-large-vtk-files-in-the-windows-version/8199/13 "2021-10-19T05:37:15Z")
Is it not possible to zip that file? I certainly won’t be pulling down 3.5Gb.
---
### Author:  [@vmajor](https://discourse.paraview.org/u/vmajor)
#### Post date: [October 19, 2021, 5:37am UTC](https://discourse.paraview.org/t/error-reading-large-vtk-files-in-the-windows-version/8199/14 "2021-10-19T05:37:32Z")
🙂 Let me try
---
### Author:  [@vmajor](https://discourse.paraview.org/u/vmajor)
#### Post date: [October 19, 2021, 5:50am UTC](https://discourse.paraview.org/t/error-reading-large-vtk-files-in-the-windows-version/8199/15 "2021-10-19T05:50:02Z")
It is now 2.48Gb: [https://velocite-public.s3.fr-par.scw.cloud/domain\_00010000.zip?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=SCW4RPBSRG82A0JQQSTB%2F20211019%2Ffr-par%2Fs3%2Faws4\_request&X-Amz-Date=20211019T054859Z&X-Amz-Expires=3596&X-Amz-Signature=f9ed586080046ca85380cfe70218dc5c1df575efba945601c56462b31814dd4d&X-Amz-SignedHeaders=host](https://velocite-public.s3.fr-par.scw.cloud/domain_00010000.zip?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=SCW4RPBSRG82A0JQQSTB%2F20211019%2Ffr-par%2Fs3%2Faws4_request&X-Amz-Date=20211019T054859Z&X-Amz-Expires=3596&X-Amz-Signature=f9ed586080046ca85380cfe70218dc5c1df575efba945601c56462b31814dd4d&X-Amz-SignedHeaders=host)
---
### Author:  [@todoooo](https://discourse.paraview.org/u/todoooo)
#### Post date: [October 19, 2021, 6:20am UTC](https://discourse.paraview.org/t/error-reading-large-vtk-files-in-the-windows-version/8199/16 "2021-10-19T06:20:56Z")
What’s the difference between the 162Mb file and this one? Apart from size.
---
### Author:  [@vmajor](https://discourse.paraview.org/u/vmajor)
#### Post date: [October 19, 2021, 6:23am UTC](https://discourse.paraview.org/t/error-reading-large-vtk-files-in-the-windows-version/8199/17 "2021-10-19T06:23:29Z")
Both files are created by the same CFD solver so there should be no differences besides the size.
---
### Author:  [@todoooo](https://discourse.paraview.org/u/todoooo)
#### Post date: [October 19, 2021, 6:24am UTC](https://discourse.paraview.org/t/error-reading-large-vtk-files-in-the-windows-version/8199/18 "2021-10-19T06:24:42Z")
So basically just a larger physical domain rather than more time steps?
---
### Author:  [@vmajor](https://discourse.paraview.org/u/vmajor)
#### Post date: [October 19, 2021, 6:26am UTC](https://discourse.paraview.org/t/error-reading-large-vtk-files-in-the-windows-version/8199/19 "2021-10-19T06:26:55Z")
Yes, it is the identical domain. The smaller file represents the results on the surface of the object, while the domain contains the results for the volume outside of the object.
---
### Author:  [@todoooo](https://discourse.paraview.org/u/todoooo)
#### Post date: [December 21, 2021, 2:46am UTC](https://discourse.paraview.org/t/error-reading-large-vtk-files-in-the-windows-version/8199/20 "2021-12-21T02:46:55Z")
@vmajor This link has expired. Please repost it (preferably 7zip compressed) and I will have a look at it over xmas.
[Next page](https://discourse.paraview.org/t/error-reading-large-vtk-files-in-the-windows-version/8199.md?page=2)