One other perculiar thing that happened on there after the failed
syspatch was this, but I'm going to assume I did a ctrl-C before
something had finished running, while I was repeating syspatch attempts.
Running security(8):
Checking special files and directories.
Output format is:
filename:
criteria (shouldbe, reallyis)
usr/sbin:
gid (0, 7)
mtree special: exit code 2
On 2025-06-20 13:13, David Diggles wrote:
Thanks.
Yeah probably not critical, I'm mainly using it for its serial ports,
for console access to other devices. Backing up state tables was just a
secondary role since it has the NICs available, I added it in to an
existing CARP pair.
No other services on it.
I'll swap out that CF sometime and test the theory.
On 2025-06-20 12:54, obs...@loopw.com wrote:
On Fri, 20 Jun 2025 12:42:06 +1000
David Diggles <da...@elven.com.au> wrote:
This is the disk space available on mine.
Filesystem Size Used Avail Capacity Mounted on
/dev/wd0a 1021M 144M 826M 15% /
/dev/wd0e 1.9G 22.7M 1.8G 2% /home
/dev/wd0d 2.9G 2.4G 403M 86% /usr
Doesn't seem like space, but theres some lack of protections going on
with your filesystem as is (probably doesnt matter so much for your
box
if its just a firewall with no public services)
your theory of the CF going out might be valid there. Those things
aren't (usually) specced for high write cycles like _some_ modern
nvme/ssd are.
