What's going on here? I've been getting these entries occasionally in my security log for a while now. It doesn't happen everyday, and doesn't seem to correlate with anything I'm doing with the NAS.
I have snapshots set for daily to keep two weeks and weekly to keep two months on media, so I think the first entry dealing with the snapshot from the 17th is the deletion of it, but I'm not sure why the rest are showing up or what really any of the other lines mean given that some of my other datasets have identical snapshot settings and do not appear anywhere in this message.
Here is another one from a while ago when some other datasets showed up in the daily run.
I suppose this could be expected behavior of some kind that I'm unable to understand...
I have snapshots set for daily to keep two weeks and weekly to keep two months on media, so I think the first entry dealing with the snapshot from the 17th is the deletion of it, but I'm not sure why the rest are showing up or what really any of the other lines mean given that some of my other datasets have identical snapshot settings and do not appear anywhere in this message.
Code:
freenas.local changes in mounted filesystems: --- /var/log/mount.today 2013-07-30 03:01:01.000000000 -0700 +++ /tmp/security.LBgWb4OD 2013-07-31 03:01:01.000000000 -0700 @@ -9,7 +9,6 @@ bluemesa/jail /mnt/bluemesa/jail zfs rw,noatime,nfsv4acls 0 0 bluemesa/logs /mnt/bluemesa/logs zfs rw,noatime,nfsv4acls 0 0 bluemesa/media /mnt/bluemesa/media zfs rw,noatime,nfsv4acls 0 0 -bluemesa/media@auto-20130717.0000-2w /mnt/bluemesa/media/.zfs/snapshot/auto-20130717.0000-2w zfs ro,nosuid,noatime,nfsv4acls 0 0 bluemesa/media@auto-20130718.0000-2w /mnt/bluemesa/media/.zfs/snapshot/auto-20130718.0000-2w zfs ro,nosuid,noatime,nfsv4acls 0 0 bluemesa/media@auto-20130719.0000-2w /mnt/bluemesa/media/.zfs/snapshot/auto-20130719.0000-2w zfs ro,nosuid,noatime,nfsv4acls 0 0 bluemesa/media@auto-20130720.0000-2w /mnt/bluemesa/media/.zfs/snapshot/auto-20130720.0000-2w zfs ro,nosuid,noatime,nfsv4acls 0 0 Checking for uids of 0: root 0 Checking for passwordless accounts: Checking login.conf permissions: Checking for ports with mismatched checksums: freenas.local login failures: freenas.local refused connections: -- End of security output --
Here is another one from a while ago when some other datasets showed up in the daily run.
Code:
freenas.local changes in mounted filesystems: --- /var/log/mount.today 2013-06-22 03:01:01.000000000 -0700 +++ /tmp/security.Zrx5GPe3 2013-06-23 03:01:01.000000000 -0700 @@ -5,7 +5,6 @@ /dev/ufs/FreeNASs4 /data ufs rw,noatime 2 2 bluemesa /mnt/bluemesa zfs rw,nfsv4acls 0 0 bluemesa/games /mnt/bluemesa/games zfs rw,noatime,nfsv4acls 0 0 -bluemesa/games@auto-20130609.0000-2w /mnt/bluemesa/games/.zfs/snapshot/auto-20130609.0000-2w zfs ro,nosuid,noatime,nfsv4acls 0 0 bluemesa/games@auto-20130610.0000-2w /mnt/bluemesa/games/.zfs/snapshot/auto-20130610.0000-2w zfs ro,nosuid,noatime,nfsv4acls 0 0 bluemesa/games@auto-20130611.0000-2w /mnt/bluemesa/games/.zfs/snapshot/auto-20130611.0000-2w zfs ro,nosuid,noatime,nfsv4acls 0 0 bluemesa/games@auto-20130612.0000-2w /mnt/bluemesa/games/.zfs/snapshot/auto-20130612.0000-2w zfs ro,nosuid,noatime,nfsv4acls 0 0 @@ -21,7 +20,6 @@ bluemesa/gents /mnt/bluemesa/gents zfs rw,noatime,nfsv4acls 0 0 bluemesa/logs /mnt/bluemesa/logs zfs rw,noatime,nfsv4acls 0 0 bluemesa/media /mnt/bluemesa/media zfs rw,noatime,nfsv4acls 0 0 -bluemesa/media@auto-20130609.0000-2w /mnt/bluemesa/media/.zfs/snapshot/auto-20130609.0000-2w zfs ro,nosuid,noatime,nfsv4acls 0 0 bluemesa/media@auto-20130610.0000-2w /mnt/bluemesa/media/.zfs/snapshot/auto-20130610.0000-2w zfs ro,nosuid,noatime,nfsv4acls 0 0 bluemesa/media@auto-20130611.0000-2w /mnt/bluemesa/media/.zfs/snapshot/auto-20130611.0000-2w zfs ro,nosuid,noatime,nfsv4acls 0 0 bluemesa/media@auto-20130612.0000-2w /mnt/bluemesa/media/.zfs/snapshot/auto-20130612.0000-2w zfs ro,nosuid,noatime,nfsv4acls 0 0 Checking for uids of 0: root 0 Checking for passwordless accounts: Checking login.conf permissions: Checking for ports with mismatched checksums: freenas.local login failures: freenas.local refused connections: -- End of security output --
I suppose this could be expected behavior of some kind that I'm unable to understand...