Nano / ro rw sometimes?

periko

Hi people.

I have running pfsense 2.0.1 on some clients, there I run squid(NO CACHE), I had seen some behaviour that maybe I still don't understand and maybe someone here can give more info and learn more from this great OS.

I had seen that sometimes went pfsense reboot the partitions are mounted like this:

/dev/ufs/pfsense0 on / (ufs, local, noatime, synchronous)
devfs on /dev (devfs, local)
/dev/md0 on /tmp (ufs, local)
/dev/md1 on /var (ufs, local)
/dev/ufs/cf on /cf (ufs, local, noatime, synchronous)
devfs on /var/dhcpd/dev (devfs, local)
/ ==> rw

Others

/dev/ufs/pfsense0 on / (ufs, local, noatime, read-only, synchronous)
devfs on /dev (devfs, local)
/dev/md0 on /tmp (ufs, local)
/dev/md1 on /var (ufs, local)
/dev/ufs/cf on /cf (ufs, local, noatime, read-only, synchronous)
devfs on /var/dhcpd/dev (devfs, local)
/ ==> ro

This are different machines, the problem for me is that in those boxes I have squid+sarg working beautiful, but some times went I need to restart the systems, is something that doesn't happen normally, the system(s) mount / with ro and don't let sarg save the reports.

I would like to understand why this happen, I will appreciated this a lot.

pfsense 2.0.1 nano on alix/neoware.

stephenw10

The nanobsd image is supposed to mount / as read only. It is remounted RW when required.
Where are you checking the mount status? It can make a difference.

Steve

periko

Hi stephenw10.

Console.

How does he decide went to do this?

Thanks!!!

stephenw10

/ and /cf are remounted RW whenever pfSense has to write out its config file or a package requires it. The package system allows this to happen. RRD data is periodically written also.
From the console should show RO unless the card is being written. Checking from the GUI command screen will remount it first.

Steve

periko

I need to work more with my box, I nomally need to let sarg write his reports in /usr/local/www/..
Here is where a detect this small behaviour, thanks stephenw10.

stephenw10

This could be an issue with the sarg package rather than the nano image. I don't use it so I can't comment. Perhaps start a new thread in packages.

Steve

jimp

There has been quite a bit of cleanup in that code in 2.1 as well, it's possible there is an issue with 2.0.x yet.

periko

Just to add, I setup sarg by hand not using the packages from pfsense, because the package creator told that all the options where available for Full install not nano and I setup sarg on nano before he build the package.
Not a big deal, now I know a little more from pfsense and know how to fix this small setting ;D
Thanks for your help guys :)

phil.davis

There were some conditions when squid(2) and squid3 could leave the filesystem in RW on nanobsd. I fixed these up a week or 2 ago. If you have reinstalled squid or squid3 recently then you should have got these fixes, even on 2.0.1. Now squid/squid3 should always leave the "/" and "/cf" filesystems in RO on nanobsd after finishing its installation/configuration/startup. This is a good thing for nanobsd.
If anyone was relying on the previous (undesirable, accidental) RW behaviour, then they will notice that they can no longer write to places like "/usr". In that case, on-the-run/temp files need to go in "/var" somewhere. When something really needs to be saved and survive reboot, then it needs calls to conf_mount_rw() and then conf_mount_ro().
I am not a Sarg user just yet, so I am not familiar with what it is doing with saving reports on nanobsd.