• Version 2.2.6 on an Intel 2500CC using a flash drive

    I am getting very slow response to "save" buttons and other such things when making changes to the configurator, often a minute or two before it comes back.

    One example was Diagnostics>Command Prompt, running just a "date" command takes over a minute to complete, while doing it on the console is instantaneous. (BTW just playing with the date command in both cases, it appears the command is actually executed right away by the gui; it's the reporting back of the results that is slow.)

    It happens when making changes to the firewall too, including moving firewall rules up and down.

    I found this complaint, but nothing else:
    OK this too… still doesn't explain slow date command:

    I think it started approximately with 2.2 or so. Before that everything was snappy. I just put up with it up till now but making substantial changes is pretty painful, so now I'm bitching.  :)  FWIW I am using dnsmasq.

  • The mechanism for disk writes in pfsense for nanobsd was changed in 2.2.3 or somewhere around there.  Net effect was exactly what you are describing but it should have been fixed in 2.2.4 if memory serves.  Fact that you are using 2.2.6 I would not think you should be seeing that behavior.  Try a different USB key.  I have the same chipset (BLKD2500CCE Intel Desktop Board D2500CC) but I'm using a USB to SATA flash card adapter SYBA SD-ADA50024 and a WinTec FileMate 8GB 3FMCF8GBS-R compact flash card.  My backups are several Kingston DataTraveler USB keys (if the sata to USB dies) but I haven't used those enough (other than just booting to confirm functionality) enough to know if they have the slow down you describe or not.


    The forcesync patch for https://redmine.pfsense.org/issues/2401 is still considered harmful to the filesystem and has been kept out. As such, there may be some noticeable slowness with NanoBSD on certain slower disks, especially CF cards and to a lesser extent, SD cards. If this is a problem, the filesystem may be kept read-write on a permanent basis using the option on Diagnostics > NanoBSD. With the other above changes, risk is minimal. We advise replacing the affected CF/SD media by a new, faster card as soon as possible. https://redmine.pfsense.org/issues/4814

  • This post is deleted!