Changes to RAM Disk Size not affecting actual filesystem size

juanzelli

@SteveITS Yes, I reboot each time I enable/disable or change values as I trial-and-error things attempting to get it to work. On this same unit (4100) over the past year, I've used the tmpfs stuff several times. I've been on and off with it trying things out. For example, I know I modified things when I was using pfBlockerNG and it needed a lot more room. I know I reduced those modifications when I removed pfBlockerNG.

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

provels

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...

juanzelli

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.

jimp

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

juanzelli

@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.

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.

SteveITS

@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)

juanzelli

@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

SteveITS

٩(͡๏̯͡๏)۶

(╯°□°）╯ ︵ ┻━┻

stephenw10

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