What does the flash plugin do with folders that are too large for RAM?

    • OMV 4.x

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • What does the flash plugin do with folders that are too large for RAM?

      I have a program installed that generates lots of log data (gigabytes-worth). The program writes the logs to /var/log and I am wondering how the flash plugin handles the log folder when it gets to be too large for RAM. Will it write the data permanently to the disk and clear itself out, or will it just get too big and switch to using the disk as normal? I made the mistake of not using the flash plugin with the previous SSD that I had installed and it died prematurely probably because of this. I would like to avoid this happening again with my new SSD so I am going to use the plugin, but I want to make sure that I have it set up to work properly.
    • The plugin uses tmpfs which defaults to half your ram. If you fill it, it is full just like any filesystem. The difference is half your ram is full too. So, your app will just stop logging (and maybe fail depending on the app).
      omv 4.1.22 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      The plugin uses tmpfs which defaults to half your ram. If you fill it, it is full just like any filesystem. The difference is half your ram is full too. So, your app will just stop logging (and maybe fail depending on the app).
      Okay. Honestly I do not want the logs to be saved but I have not been able to figure out how to disable them so I will just live with it. I noticed that when I look at the output of df -h, there are file systems that are tmpfs, but there are also filesystems listed as folder2ram. The /var/log folder is one of the folders that is listed that way. Is that significant in any way?
    • David B wrote:

      there are file systems that are tmpfs, but there are also filesystems listed as folder2ram. The /var/log folder is one of the folders that is listed that way. Is that significant in any way?
      The filesystems listed as folder2ram are the ones controlled by folder2ram which uses tmpfs. The entries listed as tmpfs are from the OS not folder2ram.
      omv 4.1.22 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      David B wrote:

      there are file systems that are tmpfs, but there are also filesystems listed as folder2ram. The /var/log folder is one of the folders that is listed that way. Is that significant in any way?
      The filesystems listed as folder2ram are the ones controlled by folder2ram which uses tmpfs. The entries listed as tmpfs are from the OS not folder2ram.
      Oh I was not aware that tmpfs was a Linux thing. Thank you for clarifying.
    • David B wrote:

      How frequently do the folders that are stored in RAM get written to the disk?
      AFAIK only at shutdown/reboot. You need to define a cronjob that does this from time to time:

      Source Code

      1. root@espressobin:~# folder2ram -syncall
      2. will now sync all mountpoints
      3. sync of /var/log successful!
      4. sync of /var/tmp successful!
      5. sync of /var/lib/openmediavault/rrd successful!
      6. sync of /var/spool successful!
      7. sync of /var/lib/rrdcached successful!
      8. sync of /var/lib/monit successful!
      9. sync of /var/lib/php successful!
      10. sync of /var/lib/netatalk/CNID successful!
      11. sync of /var/cache/samba successful!
      Display All
      No more contributions to this project until 'alternative facts' (AKA ignorance/stupidity) are gone
    • tkaiser wrote:

      AFAIK only at shutdown/reboot
      Correct.

      tkaiser wrote:

      You need to define a cronjob that does this from time to time:
      Only if you care about the log files and/or monitoring data.
      omv 4.1.22 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • tkaiser wrote:

      David B wrote:

      How frequently do the folders that are stored in RAM get written to the disk?
      AFAIK only at shutdown/reboot. You need to define a cronjob that does this from time to time:

      ryecoaaron wrote:

      Correct.

      tkaiser wrote:

      You need to define a cronjob that does this from time to time:
      Only if you care about the log files and/or monitoring data.
      Excellent, thank you! I only care about saving the graph data so I added an hourly cron job that runs folder2ram -sync 5. This outputs:

      Source Code

      1. will sync only mountpoint 5
      2. sync of /var/lib/rrdcached successful!