Log block checksum in SQL Server

Starting with SQL2005, checksum checksum is added as an option for page checksums, the most widely known two checksum options are the checksum options and page validation checksum options at backup time

Another option that less people know about is the log block checksum

What is log block?

Log Block has already made it clear in the article Song wrote.

Log block is the smallest unit of journal write persistence storage, with log block sizes ranging from 512 bytes to 60K, depending on the size of the transaction.

Log blocks that have not been written to the persistent storage in memory are known as in-flight logs. The following two factors determine the size of the log block:

Transaction commit or ROLLBACK LOG block full 60K forces flush to persistent storage to ensure Wal so when a transaction is large (for example, large-area update),

Every 60K becomes a log block write persistent storage. For many small transactions, commit or rollback becomes a block write-persistence store, so depending on the size of the transaction,

The LOG block size is also different.

You know page checksum is the page where the checksum is written to disk, and the log block checksum is actually the log block of the checksum write disk.

Because when log block written to disk may also be corrupted, so also need to check, I think the log block checksum check the importance of as much as the page check

Because SQL Server relies on logs to ensure transactional consistency, how can you rely on these logs for Redo,undo log if the logs are corrupted??