Shulou(Shulou.com)06/01 Report--

Please indicate the source of the original reprint

The error is as follows: MYSQL does not start properly

2017-09-22 10:39:05 21409 [Note] InnoDB: Database was not shutdown normally2017-09-22 10:39:05 21409 [Note] InnoDB: Starting crash recovery.2017-09-22 10:39:05 21409 [Note] InnoDB: Reading tablespace information from the .ibd files...2017-09-22 10:39:05 21409 [ERROR] InnoDB: Space id in fsp header 1416128883 but in the page header 824195850

I once wrote such an article as follows:

InnoDB: Error: space id and page n:o stored in the page?

Http://blog.itpub.net/7728585/viewspace-2121548/

But the above article is only an artificial simulation, in fact, it is much more serious in the production situation, basically the physical order of the block. Today, some netizens asked me this question. In fact, this problem generally involves the physical damage of the block. It is unlikely to be repaired. Let's take a look at the wrong location of the source code:

/ * Reads the space id from the first page of a tablespace.@return space id ULINT UNDEFINED if error * / ulintfsp_header_get_space_id (/ * = * / const page_t* page) / *! < in: first page of a tablespace * / {ulintfsp_ id Ulint id; fsp_id = mach_read_from_4 (FSP_HEADER_OFFSET + page + FSP_SPACE_ID); id = mach_read_from_4 (page + FIL_PAGE_ARCH_LOG_NO_OR_SPACE_ID); DBUG_EXECUTE_IF ("fsp_header_get_space_id_failure", id = ULINT_UNDEFINED;); if (id! = fsp_id) {ib::error ()

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.