Linux Debian Jessie based Arch is armv7l kernel is 4.4.14-v7+ tar (GNU tar) 1.27.1
We have an archive,
config.tar.gz, which replaces already existing config files. Extraction was done via ssh on the device with
tar -xzvf config.tar.gz -C /
The archive is packed with absolute paths so this is normally OK (for this setup). The same procedure was done for 14 similar devices, which are identically configured and have identical hardware and software on them.
One device, however, was unable to write the config files, it just replaced those files with files of same name and
0 byte size.
After that extraction, a manual reboot was done to have all newly extracted configuration files work with the custom services we use.
The drive itself doesn't seem to be broken, no inode issue, no write error, no issue with not enough space or similar related problems.
The hard drive (actually an sdcard) does not show any issues and is perfectly usable.
Sadly, the output of the tar command is not available anymore.
The usual logs (syslog, messages, auth, daemon, journalctl, custom logs we create), all show nothing which seems related.
I have the sdcard here but cannot reproduce the error with either that card or another with the same configuration.
What could have caused this? How can I ensure it doesn't happen again?