New Feature: /tmp and /var RAM disks on Full installs; /tmp and /var resizing
-
is it possible to create a option for a third RamDisk?
So we can choose Squid/HAVP/etc for using this space for caching!
so the normal usage of /tmp and /var is not affected?!No, there is no option for that, and probably won't be. Not something common enough to warrant doing. Just config squid to use more memory cache and not a disk cache in a RAM disk. That's a discussion for a different thread though.
-
@w0w:
Updated to the latest snapshot via automatic update. No option in System-Advanced-Mics.
What am I doing wrong?Which option is not there?
On nanobsd, the checkbox "Use memory file system for /tmp and /var" does not appear, because it is not optional - it always "Uses memory file system for /tmp and /var".I have full install done on ssd disk about a half of year ago
Now it shows
2.1-BETA1 (i386)
built on Wed Apr 3 04:19:20 EDT 2013
FreeBSD 8.3-RELEASE-p7This what I have in System: Advanced: Miscellaneous (see attached image)
-
You must have some other issue preventing that page from getting updated, but it's not relevant to this thread. Start a fresh thread and someone can help you investigate why a firmware update isn't updating that file.
-
The missing items are all down the end and are all items that have been added in March 2013. My nanobsd system shows them all - Skip rules when gateway is down, /tmp RAM Disk Size, /var RAM Disk Size, Periodic RRD Backup, Periodic DHCP Leases Backup.
It is just as if your /usr/local/www/system_advanced_misc.php was never updated. On your system, check if that file actually contains code for any of these items. Then as JimP recommends, start another thread to try and sort out what happened during updating. -
OK. Now I got this option activated. On reboot I see next (see image)
Any comments?
-
Hard to say exactly. I didn't see that in any of my testing. How large did you try to set the /tmp and /var disks to be? perhaps it used all your memory?
-
2GB of memory installed. 18xxMB free.
First time I have used 512MB for both RAM disks and now I left it blank, when screenshot is taken. -
Clean install from pfSense-LiveCD-2.1-BETA1-i386-20130405-0056.iso.gz
to VirtualBox with minimum config to access web settings and activate RAM disks (all fields are empty only check-box active).
Same error
-
OK that isn't from this code, it's from later in the boot process.
With this option enabled, /var is already a RAM disk. The error comes from mdmfs trying to make a /var/run RAM disk, and failing.
-
@w0w:
2GB of memory installed. 18xxMB free.
I presume that is on the system. How much RAM have you assigned to the VM running pfSense?
-
@w0w:
2GB of memory installed. 18xxMB free.
I presume that is on the system. How much RAM have you assigned to the VM running pfSense?
Why are you asking? jimp already found why mdmfs is failing
Anyway it's 4GB of memory in VM -
@w0w:
jimp already found why mdmfs is failing
I can see a report in this topic that mdmfs is failing but I don't see an explanation in this topic of why it is failing so I assumed the issue was still open.
-
@w0w:
jimp already found why mdmfs is failing
I can see a report in this topic that mdmfs is failing but I don't see an explanation in this topic of why it is failing so I assumed the issue was still open.
See my post here: http://forum.pfsense.org/index.php/topic,59941.msg328113.html#msg328113
This should be solved after a commit I made this afternoon. Nothing was actually failing fatally, it was just erroring out on a part that wasn't necessary in this config
-
is it possible to create a option for a third RamDisk?
So we can choose Squid/HAVP/etc for using this space for caching!
so the normal usage of /tmp and /var is not affected?!No, there is no option for that, and probably won't be. Not something common enough to warrant doing. Just config squid to use more memory cache and not a disk cache in a RAM disk. That's a discussion for a different thread though.
Jepp: http://forum.pfsense.org/index.php/topic,60944.0.html
Btw: Many thank's for your work and implementation of nice new features! I've read your book and would be happy to read the next version with pfS 2.1 :)
-
For all those missing this functionality, I found that even after updates it was not showing up. The reason I found was that I had the option to gitsync at the end of update. This either replaced the file or in my case never ran properly after the repository change. To resolve this, rename /root/pfsense to anything else, I chose pfsense.old, then "vi /etc/phpshellsessions/gitsync" changing the "$GIT_REPO" to "git://github.com/pfsense/pfsense.git". Once I did this and played back gitsync, I have this option available to me.
-
For all those missing this functionality, I found that even after updates it was not showing up. The reason I found was that I had the option to gitsync at the end of update. This either replaced the file or in my case never ran properly after the repository change. To resolve this, rename /root/pfsense to anything else, I chose pfsense.old, then "vi /etc/phpshellsessions/gitsync" changing the "$GIT_REPO" to "git://github.com/pfsense/pfsense.git". Once I did this and played back gitsync, I have this option available to me.
http://forum.pfsense.org/index.php/topic,60805.0.html
-
Sure . that works also. Perhaps it is better to disable gitsync on firmware upgrade for now.
-
Today accidentally I found that I have the same problem like described here - http://forum.pfsense.org/index.php?action=profile;u=232265;sa=showPosts and the reason why CUPS really wants directory to be created manually is that I am using ramdisk feature. When I disable it, CUPS logs are empty and directories are created automatically. This looks like some non critical "cosmetic" bug/feature that can affect other packages too, so be careful before adding something that uses var or tmp.
