On Tue, May 17, 2011 at 10:22 AM, Shibashish <[email protected]> wrote:
> > On Tue, May 17, 2011 at 1:15 PM, Warren Baker <[email protected]> wrote: > >> >> Remember that there are active sessions which are in the firewall state >> table, these sessions will continue to work regardless of your changes until >> these sessions expired. I am no expert on the server load balancer so I am >> not sure whether states are removed when changes are made to pool (i know >> states are changed when there is a server that is marked as down). So >> someone else will need to answer on that. >> >> >> > *To add, I did flush out all the states, i.e. did a "reset states". I > missed writing this.* > > >> This indicates that there was a hard reboot and the system was not cleanly >>> shutdown due to a power failure, OS crash or similar. >> >> So on the next boot a file system check took place to ensure the >> consistency of the file system which would have fixed any problems >> automatically. >> >> *Does pfSense do a fsck on reboot/boot... can you/someone please confirm. > * > pfSense will do a file system check on every reboot, this is to ensure the file system is healthy. If it is not then it will indicate this and execute a fsck to fix the problem(s). > >> This would then have happened prior to the 45 days. >> >> *I did a touch and rm after seeing the issue and the log file. The > filesystem was writeable.* > Correct - as the fsck was successful. > >> >> >>> 2. Shouldn't the webconfigurator show warnings/errors if this happens? >>> >> >> >> No since fsck fixes the file system on boot. If it didn't or could not fix >> it, the system would not boot and drop you to a shell. You would then have >> to manually fix it. >> >> *My point was that, shouldn't webconfigurator show a warning/error that > fs is readonly and new config cannot be saved/activated.* > The fs was not readonly as you mentioned above that you could touch and rm. -- .warren
