~dunkhan


#51 Large file count causes OS issues 2 months ago

Comment by ~dunkhan on ~mil/mepo-tickets

I had to do a bit of reading to know what inodes are and how they work, but yes, that would fit what I experienced. You can actually increase the inodes in ext4 during formatting, just not dynamically afterwards. With regard to sending a multifile container patch... I was about to say my knowledge of c/c++ is limited but I checked and it is written in Zig. My knowledge of that is even more limited but the temptation to try out a brand new language might motivate me to look into it anyway.

#51 Large file count causes OS issues 3 months ago

Comment by ~dunkhan on ~mil/mepo-tickets

So you dont think a tarball or some other multi-file container is viable? I would like to store the whole city where I live and that takes several Gb and millions of files. Even just running ls in the cache directory hangs up my machine. Thanks for the info on the max zoom level, I will try that. Also since updating (had to reflash the whole memory as deleting that many files takes hours) mepo no longer shows the menu in sxmo, it has no menu items. Is this a known issue or should I report that separately?

#51 Large file count causes OS issues 3 months ago

Ticket created by ~dunkhan on ~mil/mepo-tickets

Description: postmarketOS sxmo edge 20220921-1858 After the tile cache reaches around 2 million files (rough estimate, not possible to count exactly) the operating system starts returning errors that the hard drive is full for any write actions. My best guess is that the function that is checking disk space is timing out trying to measure the size of the files. This could be a bug in the operating system and I may try to report it there too, but the real question is do we need to be creating that many files? It seems like it would be more sensible to create a tarball or a series of tarballs.

It might also be useful to have a maximum cache zoom level in the config to reduce the cache size as the top zoom levels are exponentially more data and not especially necessary for navigation.

Reproduction: Simply connect the device to fast internet and use the download region function to download a large amount of data. It can take a few hours depending on the connection speed. To test if the reproduction is complete simply try to create an empty file on the same drive where the mepo cache is present.

#42 Out of memory crash while downloading 3 months ago

on ~mil/mepo-tickets

Thanks ~dunkhan - closing since this is no longer reproducible.

Opened #44 separately to handle automatically switching to software rendering if hw renderer is unavailable as this was the root cause of this issue.

#42 Out of memory crash while downloading 4 months ago

Comment by ~dunkhan on ~mil/mepo-tickets

I checked this myself. After installing edge pmos this issue was no longer reproducible. I think we can close this bug.

#42 Out of memory crash while downloading 4 months ago

Comment by ~dunkhan on ~mil/mepo-tickets

Pinephone beta edition Sxmo

  1. Flash STABLE image from postmarket os download page, this specific image: https://images.postmarketos.org/bpo/v22.06/pine64-pinephone/sxmo-de-sway/20220914-0518/20220914-0518-postmarketOS-v22.06-sxmo-de-sway-1.9.0-pine64-pinephone.img.xz
  2. Install mepo from the EDGE repository by settings the --repository flag on the apk command
  3. run mepo
  4. set the view to cover a large area (30x30 km of a built up city seems to be plenty)
  5. download current bounds

Please note I am running stable sxmo with edge mepo, if this is required to reproduce the issue it might be a bug in sxmo and it might already be fixed.

#42 Out of memory crash while downloading 4 months ago

Ticket created by ~dunkhan on ~mil/mepo-tickets

PinePhone with Postmarket OS sxmo While attempting to download a large area the application crashes with: DRM_IOCTL_MODE_CREATE_DUMB failed: Out of memory

It is possible I misunderstood how the offline feature is supposed to work but I was hoping it would save data to permanent storage and retain it between sessions. This error suggests it is trying to hold everything in RAM. It crashes after around 200mb