Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Changes to RAM Disk Size not affecting actual filesystem size

    Scheduled Pinned Locked Moved webGUI
    18 Posts 6 Posters 1.4k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • provelsP
      provels
      last edited by

      FWIW, I don't see that behavior on mine with 24.11. And the only reason they're so big is I have 16GB and it's just me: Sysadmin, User, Night Cleanup...

      d11ff6b4-5428-45f4-a343-f49959ad18c6-image.png

      Peder

      MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
      BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

      1 Reply Last reply Reply Quote 1
      • juanzelliJ
        juanzelli @juanzelli
        last edited by

        This weekend, I guess I'll factory reset, restore the config.xml, and see if that helps.

        Nope. Factory reset and restore of the configuration didn't help.

        Netgate 4100 and HPE InstantOn network at home

        1 Reply Last reply Reply Quote 0
        • jimpJ
          jimp Rebel Alliance Developer Netgate
          last edited by

          I can't seem to replicate any issue here. I set a size, click JS alert to go to the reboot page, then confirm the reboot there and when it starts back up it's using the size from the configuration.

          If you run the following commands from a shell prompt, what output do you get?

          $ /usr/local/sbin/read_xml_tag.sh string system/use_mfs_tmp_size
          $ /usr/local/sbin/read_xml_tag.sh string system/use_mfs_var_size
          

          Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

          Need help fast? Netgate Global Support!

          Do not Chat/PM for help!

          juanzelliJ 2 Replies Last reply Reply Quote 0
          • juanzelliJ
            juanzelli @jimp
            last edited by

            @jimp Thank you for investigating. However, I cannot provide the results. I've replaced the unit with another system for other testing. I'll circle back around to provide the results you requested eventually.

            Netgate 4100 and HPE InstantOn network at home

            1 Reply Last reply Reply Quote 0
            • juanzelliJ
              juanzelli @jimp
              last edited by juanzelli

              @jimp said in Changes to RAM Disk Size not affecting actual filesystem size:

              If you run the following commands from a shell prompt, what output do you get?

              After reinstalling from USB, uploading my entire config.xml, and rebooting...

              [24.11-RELEASE][root@thewall.home.arpa]/root: /usr/local/sbin/read_xml_tag.sh string system/use_mfs_tmp_size
              100
              [24.11-RELEASE][root@thewall.home.arpa]/root: /usr/local/sbin/read_xml_tag.sh string system/use_mfs_var_size
              200
              [24.11-RELEASE][root@thewall.home.arpa]/root: df -h /tmp /var
              Filesystem    Size    Used   Avail Capacity  Mounted on
              tmpfs          40M    280K     40M     1%    /tmp
              tmpfs          60M     19M     41M    32%    /var
              [24.11-RELEASE][root@thewall.home.arpa]/root: uptime
              11:36AM  up 3 mins, 3 users, load averages: 0.87, 0.58, 0.25
              

              This config.xml has seen a few major versions and dev/beta versions. I'm wondering if there is some orphan artifact in the config.xml causing issues. Looking at the file in VisualStudio shows no formatting or other issues.

              Netgate 4100 and HPE InstantOn network at home

              S 1 Reply Last reply Reply Quote 0
              • S
                SteveITS Galactic Empire @juanzelli
                last edited by

                @juanzelli It's OK on my 2100 which I updated:

                tmpfs 512M 796K 511M 0% /tmp
                tmpfs 1.0G 48M 976M 5% /var

                If you aren't actively using this unit anymore, you could potentially reset it to defaults (Diagnostics menu) and try a RAM disk, then restore either the full config file or parts of it afterwards.

                Wondering out loud, could there be any sort of error checking that fails while creating the RAM disk and uses the default size? (I would think it would just fail to create)

                Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                Upvote 👍 helpful posts!

                juanzelliJ 1 Reply Last reply Reply Quote 0
                • juanzelliJ
                  juanzelli @SteveITS
                  last edited by

                  @SteveITS Ok. This is the sequence of events I just performed...

                  1 - Factory Defaults from Diagnostics and reboot
                  2 - Set my RAM disk settings and reboot
                  3 - RAM disk sizes still ignoring my settings
                  4 - Factory Reset via hardware button
                  5 - Set my RAM disk settings and reboot
                  6 - RAM disk sizes still ignoring my settings
                  7 - Reinstall from USB and chose 24.11
                  8 - Set my RAM disk settings and reboot
                  9 - RAM disk sizes still ignoring my settings
                  10 - Reinstall from USB and chose 24.03 (why not try?)
                  11 - Set my RAM disk settings and reboot
                  12 - SUCCESS! My RAM disk sizes stuck
                  13 - Upgraded to 24.11 via GUI and reboot
                  14 - My RAM disk sizes remained
                  15 - Restored my config.xml and reboot
                  16 - My RAM disk sizes continue to remain as expected

                  Netgate 4100 and HPE InstantOn network at home

                  S 1 Reply Last reply Reply Quote 0
                  • S
                    SteveITS Galactic Empire @juanzelli
                    last edited by

                    ٩(͡๏̯͡๏)۶

                    (╯°□°)╯ ︵ ┻━┻

                    Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                    When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                    Upvote 👍 helpful posts!

                    1 Reply Last reply Reply Quote 1
                    • stephenw10S
                      stephenw10 Netgate Administrator
                      last edited by

                      If you change the size after upgrading do they now change after rebooting?

                      1 Reply Last reply Reply Quote 0
                      • S SteveITS referenced this topic on
                      • J
                        jdoveSense @juanzelli
                        last edited by

                        @juanzelli Still a prob for me June 6, 2025

                        S 1 Reply Last reply Reply Quote 0
                        • S
                          SteveITS Galactic Empire @jdoveSense
                          last edited by

                          @jdoveSense There's a bug that affects some models and/or installs. As above, not my 2100, but definitely our 4200 at work.

                          https://redmine.pfsense.org/issues/16023
                          from https://docs.netgate.com/pfsense/en/latest/releases/25-03.html#operating-system

                          Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                          When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                          Upvote 👍 helpful posts!

                          J 1 Reply Last reply Reply Quote 0
                          • J
                            jdoveSense @SteveITS
                            last edited by

                            @SteveITS Yeah, this is a tough one for me, I hope it's officially reported as a bug; I'll have to check on it later. Thanks for the headsup.

                            S 1 Reply Last reply Reply Quote 0
                            • S
                              SteveITS Galactic Empire @jdoveSense
                              last edited by

                              @jdoveSense Reported and resolved, see above. ;)

                              Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                              When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                              Upvote 👍 helpful posts!

                              J 1 Reply Last reply Reply Quote 1
                              • J
                                jdoveSense @SteveITS
                                last edited by

                                @SteveITS Thank you Steve, looks like you went through a lot of troubleshooting to get that to work. Nice going. I think that's a good workaround that I may try over the weekend. That said, I'm not sure, from Netgate's perspective, they should put that in the resolved category as not every user will come across this thread of always have direct and easy access to the hardware console. For the time being, I just went in to /etc/rc.ramdisk_functions.sh and set RAMDISK_DEFAULT_SIZE_ to my values... also not the best resolution, but it works for now.

                                1 Reply Last reply Reply Quote 1
                                • First post
                                  Last post
                                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.