Freenas Replication - Daily Security Email - Filesystem Changes "Read Only" an Error on my part?

[SMATHEW315]

Hello Freenas Forum,

I've been using Freenas for a few years now and currently have 2 servers (Push (CS3-NAS) and Pull (BETA-NAS)) for replication. I had a question for some of the details included in my daily security emails in regards to Filesystem changes to my "PULL" Freenas server. I know that the "PULL" server zpool is auto set to read-only to protect the received snapshot data. The System Dataset for PULL is in one of the zpools, not freenas-boot.

This is the auto generated output from my PULL server after received replicated data from the "PUSH" server.

BETA-NAS.home changes in mounted filesystems:
1,24c1,24
< beta-nas-stripe1 /mnt/beta-nas-stripe1 zfs rw,nfsv4acls 0 0
< beta-nas-stripe1/.system /var/db/system zfs rw,nfsv4acls 0 0
< beta-nas-stripe1/.system/configs-839d4bf50898424ab2b76c72b7c93def /var/db/system/configs-839d4bf50898424ab2b76c72b7c93def zfs rw,nfsv4acls 0 0
< beta-nas-stripe1/.system/cores /var/db/system/cores zfs rw,nfsv4acls 0 0
< beta-nas-stripe1/.system/rrd-839d4bf50898424ab2b76c72b7c93def /var/db/system/rrd-839d4bf50898424ab2b76c72b7c93def zfs rw,nfsv4acls 0 0
< beta-nas-stripe1/.system/samba4 /var/db/system/samba4 zfs rw,nfsv4acls 0 0
< beta-nas-stripe1/.system/syslog-839d4bf50898424ab2b76c72b7c93def /var/db/system/syslog-839d4bf50898424ab2b76c72b7c93def zfs rw,nfsv4acls 0 0
< beta-nas-stripe1/.system/webui /var/db/system/webui zfs rw,nfsv4acls 0 0
< beta-nas-zpool1 /mnt/beta-nas-zpool1 zfs rw,nfsv4acls 0 0
< beta-nas-zpool1/.system /mnt/beta-nas-zpool1/.system zfs rw,nfsv4acls 0 0
< beta-nas-zpool1/.system/configs-839d4bf50898424ab2b76c72b7c93def /mnt/beta-nas-zpool1/.system/configs-839d4bf50898424ab2b76c72b7c93def zfs rw,nfsv4acls 0 0
< beta-nas-zpool1/.system/cores /mnt/beta-nas-zpool1/.system/cores zfs rw,nfsv4acls 0 0
< beta-nas-zpool1/.system/rrd-839d4bf50898424ab2b76c72b7c93def /mnt/beta-nas-zpool1/.system/rrd-839d4bf50898424ab2b76c72b7c93def zfs rw,nfsv4acls 0 0
< beta-nas-zpool1/.system/samba4 /mnt/beta-nas-zpool1/.system/samba4 zfs rw,nfsv4acls 0 0
< beta-nas-zpool1/.system/syslog-839d4bf50898424ab2b76c72b7c93def /mnt/beta-nas-zpool1/.system/syslog-839d4bf50898424ab2b76c72b7c93def zfs rw,nfsv4acls 0 0
< beta-nas-zpool1/.system/webui /mnt/beta-nas-zpool1/.system/webui zfs rw,nfsv4acls 0 0
< beta-nas-zpool1/Backups /mnt/beta-nas-zpool1/Backups zfs rw,nfsv4acls 0 0
< beta-nas-zpool1/Home /mnt/beta-nas-zpool1/Home zfs rw,nfsv4acls 0 0
< beta-nas-zpool1/Home/*********/mnt/beta-nas-zpool1/Home/jmathew48 zfs rw,nfsv4acls 0 0
< beta-nas-zpool1/Home/*******/mnt/beta-nas-zpool1/Home/rajidpt zfs rw,nfsv4acls 0 0
< beta-nas-zpool1/Home/**********/mnt/beta-nas-zpool1/Home/smathew315 zfs rw,nfsv4acls 0 0
< beta-nas-zpool1/Plex /mnt/beta-nas-zpool1/Plex zfs rw,nfsv4acls 0 0
< beta-nas-zpool1/Software /mnt/beta-nas-zpool1/Software zfs rw,nfsv4acls 0 0
< beta-nas-zpool1/TempStor /mnt/beta-nas-zpool1/TempStor zfs rw,nfsv4acls 0 0
---
> beta-nas-stripe1 /mnt/beta-nas-stripe1 zfs ro,nfsv4acls 0 0
> beta-nas-stripe1/.system /var/db/system zfs ro,nfsv4acls 0 0
> beta-nas-stripe1/.system/configs-839d4bf50898424ab2b76c72b7c93def /var/db/system/configs-839d4bf50898424ab2b76c72b7c93def zfs ro,nfsv4acls 0 0
> beta-nas-stripe1/.system/cores /var/db/system/cores zfs ro,nfsv4acls 0 0
> beta-nas-stripe1/.system/rrd-839d4bf50898424ab2b76c72b7c93def /var/db/system/rrd-839d4bf50898424ab2b76c72b7c93def zfs ro,nfsv4acls 0 0
> beta-nas-stripe1/.system/samba4 /var/db/system/samba4 zfs ro,nfsv4acls 0 0
> beta-nas-stripe1/.system/syslog-839d4bf50898424ab2b76c72b7c93def /var/db/system/syslog-839d4bf50898424ab2b76c72b7c93def zfs ro,nfsv4acls 0 0
> beta-nas-stripe1/.system/webui /var/db/system/webui zfs ro,nfsv4acls 0 0
> beta-nas-zpool1 /mnt/beta-nas-zpool1 zfs ro,nfsv4acls 0 0
> beta-nas-zpool1/.system /mnt/beta-nas-zpool1/.system zfs ro,nfsv4acls 0 0
> beta-nas-zpool1/.system/configs-839d4bf50898424ab2b76c72b7c93def /mnt/beta-nas-zpool1/.system/configs-839d4bf50898424ab2b76c72b7c93def zfs ro,nfsv4acls 0 0
> beta-nas-zpool1/.system/cores /mnt/beta-nas-zpool1/.system/cores zfs ro,nfsv4acls 0 0
> beta-nas-zpool1/.system/rrd-839d4bf50898424ab2b76c72b7c93def /mnt/beta-nas-zpool1/.system/rrd-839d4bf50898424ab2b76c72b7c93def zfs ro,nfsv4acls 0 0
> beta-nas-zpool1/.system/samba4 /mnt/beta-nas-zpool1/.system/samba4 zfs ro,nfsv4acls 0 0
> beta-nas-zpool1/.system/syslog-839d4bf50898424ab2b76c72b7c93def /mnt/beta-nas-zpool1/.system/syslog-839d4bf50898424ab2b76c72b7c93def zfs ro,nfsv4acls 0 0
> beta-nas-zpool1/.system/webui /mnt/beta-nas-zpool1/.system/webui zfs ro,nfsv4acls 0 0
> beta-nas-zpool1/Backups /mnt/beta-nas-zpool1/Backups zfs ro,nfsv4acls 0 0
> beta-nas-zpool1/Home /mnt/beta-nas-zpool1/Home zfs ro,nfsv4acls 0 0
> beta-nas-zpool1/Home/*********/mnt/beta-nas-zpool1/Home/jmathew48 zfs ro,nfsv4acls 0 0
> beta-nas-zpool1/Home/*******/mnt/beta-nas-zpool1/Home/rajidpt zfs ro,nfsv4acls 0 0
> beta-nas-zpool1/Home/**********/mnt/beta-nas-zpool1/Home/smathew315 zfs ro,nfsv4acls 0 0
> beta-nas-zpool1/Plex /mnt/beta-nas-zpool1/Plex zfs ro,nfsv4acls 0 0
> beta-nas-zpool1/Software /mnt/beta-nas-zpool1/Software zfs ro,nfsv4acls 0 0
> beta-nas-zpool1/TempStor /mnt/beta-nas-zpool1/TempStor zfs ro,nfsv4acls 0 0
mv: rename /var/log/mount.today to /var/log/mount.yesterday: Read-only file system
mv: rename /tmp/security.tGjh4rmS to /var/log/mount.today: Read-only file system

BETA-NAS.home kernel log messages:
mv: rename /var/log/dmesg.today to /var/log/dmesg.yesterday: Read-only file system
mv: rename /tmp/security.ywoUro3z to /var/log/dmesg.today: Read-only file system

-- End of security output --

About a year ago I used to receive the same output for a while until the PULL server became unresponsive to HTTP/HTTPS connections and replication failed (connection timeouts). In fact, connecting a monitor and keyboard showed me a screen full of

mv: rename /var/log/mount.today to /var/log/mount.yesterday: Read-only file system

I was finally able to fix this by pulling up the CLI shell on PULL and setting to readonly=false and rebooting. Finally all the issues went away but I'm weary of leaving the setting off. I turned the setting back on these messages started to get emailed again daily. Any ideas or suggestions?

ps. My server info is in my signature.