" Obviously nobody with the least bit of clue would expect logs to be cleanly written on failing disks, hence this is not even a subject for discussion" exactly so if rsyslog logs are corrupted its expected but if journald logs are corrupted, its the fault of systemd, great logic
" Failing disks or filesystems are detected rightfully by the kernel, nothing else has any business doing so" so what else does?
""Different from systemd "logging", rsyslog will not make the log problem worse by using a binary format " - it doesn;t make any difference what format the logs are written in, if the location of the log file data is trashed, then its totally or partially unreadable in any format.
" and for remote logging will transfer the messages off-site." and if the system fails before rsyslog is actually running or the network is not yet loaded? rsyslog is loaded quite late in the boot process as opposed to journald