After running BackupPC for almost two decades on a dozen machines or
so, I encountered a weird file error.
Typically, the prior monthly log files for each host are
zlib-compressed.
So, if I type: file LOG.MMYYYY.z, I get:
LOG.MMYYYY.z: zlib compressed data
NOW today is Sept 1, 2022 so for each host, the file LOG.082022 gets
compressed to LOG.082022.z for each host.
However for one of my host, while the files seems to be z-lib compressed
properly (as it is binary yet readable by BackupPC_zcat), running 'file'
shows:
LOG.082022.z: Minix filesystem, V1 (big endian), 19571 zones
So for some reason 'file' detects it to be a Minix filesystem.
All my other hosts for all other prior months are just fine.
Even for this host there is no problem for LOG.082022.z on my
secondary BackupPC server.
Note the magic number for this log file is the normal (for BackupPC)
'78 5e' which is a zlib-ish type magic number but not an official one.
But I imagine since it's not official, somehow in this case the
initial sequence (including the bytes following the first 2) is
interpreted as a Minix File System.
The first 16 bytes of the file are:
785e b55d 4d6f 2337 12bd efaf 6820 879d
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
