MySQL: learning how to recover your InnoDB from corruption

By -
This is wonderful post to learn how to recover your data from Peter Zaitsev,

http://www.mysqlperformanceblog.com/2008/07/04/recovering-innodb-table-corruption/


This means that in every BTREE context, there's always a page and by using BTREE data structure, you have records stored in there as part of the page and that means you can recover your data from its tablespace.

Comments

Post a Comment

Popular posts from this blog

Converting sectors into MB - Useful in understanding the sectors in iostat in Linux

By -
Supposed you have a sector with 512 Bytes equivalent, then the formula will be just below 1 sect. 1024 Bytes 1024 KB --------- x ---------- x --------- = 2048 sect./ MB 512 Bytes 1 KB 1 MB i.e. if a sector has a 512 Bytes, commonly in a hard disk, so which means that a 1024 Bytes == 2 sector of a KiloByte. So if 2 sector is equivalent to a KiloByte (1024 Bytes), if you do the math, 2 ** 1024 / 512.0 = 2048. This is useful only understanding the iostat process in Linux.
Read more

What is Disk Contention?

By -
Okay, so let me take a note about this meaning... Disk contention occurs when multiple processes try to access the same disk simultaneously. Most disks have limits on both the number of accesses (I/O operations each second) and the amount of data they can transfer each second (I/O data rate, or  throughput ). When these limits are reached, processes must wait to access the disk. It's a situation occurring when multiple processes try to access the same disk(s) and the requests outrun the response times of the drive(s). This happens because most disks are restricted in the amount of data they can transfer and the number of accesses (I/O operations) they can handle each second. Disk contention became a more prominent problem when CPU speeds dramatically increased over the past 15 years, putting even greater demands on disk-based data storage and causing the modern data centers’ most significant operational constraint.
Read more

Installing MySQL from source: Could NOT find Curses (missing: CURSES_LIBRARY CURSES_INCLUDE_PATH)

By -
Just find this a terrible problem with my CentOS having x86_64 architecture and cmake failed to find the right library for Curses. Anyway, this is how I got the error when trying to build MySQL from source , $ cmake . -- Running cmake version 2.6.4 -- MySQL 5.6.12 -- Packaging as: mysql-5.6.12-Linux-x86_64 -- HAVE_VISIBILITY_HIDDEN -- HAVE_VISIBILITY_HIDDEN -- HAVE_VISIBILITY_HIDDEN -- Could NOT find Curses  (missing:  CURSES_LIBRARY CURSES_INCLUDE_PATH) CMake Error at cmake/readline.cmake:85 (MESSAGE):   Curses library not found.  Please install appropriate package,       remove CMakeCache.txt and rerun cmake.On Debian/Ubuntu, package name is libncurses5-dev, on Redhat and derivates it is ncurses-devel. Call Stack (most recent call first):   cmake/readline.cmake:128 (FIND_CURSES)   cmake/readline.cmake:202 (MYSQL_USE_BUNDLED_EDITLINE)   CMakeLists.txt:332 (MYSQL_CHECK_EDITLINE) -- Configuring incomplete, errors occurred! I have already installed my curses library
Read more