Add pfSense NVMe cache overlay documentation

[JonathanDLee24]

This document provides a script for creating a filesystem overlay using nullfs to mount an alternate NVMe-backed directory as the Squid cache location on pfSense systems. It includes usage instructions and a cron job setup.

[JonathanDLee24]

ok the logs are now text based as requested

[JonathanDLee24]

I created a new one with the fixes and a additional example file that was a lot of researching in pfsense to help others or bring to light issues and known limitations #46

…

On Jan 12, 2026, at 18:02, Alex Rousskov ***@***.***> wrote: @rousskov commented on this pull request. In docs/ConfigExamples/Caching/pfSensenvmecacheuse.md <#45 (comment)>: > + mount -t nullfs "${CACHE_SRC}" "${CACHE_DST}" || { + log_sys "ERROR: nullfs mount failed" + exit 1 + } + else + log_sys "nullfs already mounted" + fi + + # 5. Start squid + log_sys "Starting squid" + /usr/local/sbin/pfSsh.php playback svc start squid + + log_sys "Squid nullfs mount completed" + +## Testing should show a valid mount on reboot in logs +<img width="690" height="226" alt="Screenshot 2026-01-12 at 14 56 06" src="https://github.com/user-attachments/assets/f770a6e0-b799-47dc-89fc-d5a05e25aef5" /> It would be nice to convert this image into a markdown text table, so that we are not hosting a link to an image that we do not control. I do not know enough about GitHub user attachments to flag this as a security risk, but using text is overall better even if these attachments are not a security risk. — Reply to this email directly, view it on GitHub <#45 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2VDGN7OIXBZ7HTFT6J3CTD4GRGZ3AVCNFSM6AAAAACRPF5SNGVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTMNJTGQ2TSMRYGU>. You are receiving this because you authored the thread.

[rousskov]

ok the logs are now text based as requested

Thank you.

I created a new one with the fixes and a additional example file that was a lot of researching in pfsense to help others or bring to light issues and known limitations

Do you want to close this PR and switch to #46 (as if this PR did not exist)? Or do you want us to merge this PR first (creating merge conflicts for #46 that you would have to resolve)?

[JonathanDLee24]

Sure sorry about the issues the other one also has the text issues fixed