Hi,
yesterday and today , we encountered twice table corrupted errors, one on slave and other on master.
later, we restore table from database backup, please help confirm, this is os question or bug? thanks.

2019-09-18 2:42:43 0 [Note] InnoDB: Uncompressed page, stored checksum in field1 0, calculated checksums for field1: crc32 0, innodb 250018845, page type 17855 == INDEX.none 3735928559, stored checksum in field2 0, calculated check
sums for field2: crc32 0, innodb 301963614, none 3735928559, page LSN 1847 2662309274, low 4 bytes of LSN at page end 2662309274, page number (if stored to page already) 92068, space id (if created with >= MySQL-4.1.1 and stored alr
eady) 34
2019-09-18 2:42:43 0 [Note] InnoDB: Page may be an index page where index id is 126
2019-09-18 2:42:43 0 [Note] InnoDB: Index 126 is `idx__date` in table `db`.`tb_users_025`
2019-09-18 2:42:43 0 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the cor
ruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recove
ry.
2019-09-18 2:42:43 0 [ERROR] InnoDB: Failed to read file './db/tb_users_025.ibd' at offset 92068: Page read from tablespace is corrupted.
2019-09-18 3:04:43 0 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace db/tb_users_025 page [page id: space=34, page number=92068]. You may have to recover from a backup.
2019-09-18 3:04:43 0 [Note] InnoDB: Page dump in ascii and hex (16384 bytes)