Comments on: Data Recovery Toolkit for InnoDB Version 0.1 Released http://www.mysqlperformanceblog.com/2007/11/26/data-recovery-toolkit-for-innodb-version-01-released/ Percona's MySQL & InnoDB performance and scalability blog Sat, 11 Feb 2012 16:45:54 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: waqas http://www.mysqlperformanceblog.com/2007/11/26/data-recovery-toolkit-for-innodb-version-01-released/comment-page-1/#comment-772780 waqas Mon, 30 Aug 2010 14:52:40 +0000 http://www.mysqlperformanceblog.com/2007/11/26/data-recovery-toolkit-for-innodb-version-01-released/#comment-772780 Hello i visit your bolg thourgh google.so nice Hello i visit your bolg thourgh google.so nice

]]> By: Alfredo Herrejon http://www.mysqlperformanceblog.com/2007/11/26/data-recovery-toolkit-for-innodb-version-01-released/comment-page-1/#comment-635243 Alfredo Herrejon Fri, 21 Aug 2009 17:49:26 +0000 http://www.mysqlperformanceblog.com/2007/11/26/data-recovery-toolkit-for-innodb-version-01-released/#comment-635243 Hello I truncated a production table so I am in serious problems, i followed all the steps from the documentation at http://code.google.com/p/innodb-tools/wiki/InnodbRecoverySteps, but when I made the make command after the ./configure I got some warnings like constraints_parser.c:88: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘ulint’ constraints_parser.c: In function ‘check_fields_sizes’: constraints_parser.c:130: warning: format ‘%u’ expects type ‘unsigned int’, but argument 2 has type ‘ulint’ constraints_parser.c:144: warning: format ‘%u’ expects type ‘unsigned int’, but argument 2 has type ‘ulint’ constraints_parser.c:144: warning: format ‘%u’ expects type ‘unsigned int’, but argument 4 has type ‘ulint’ constraints_parser.c: In function ‘ibrec_init_offsets_new’: constraints_parser.c:231: warning: format ‘%i’ expects type ‘int’, but argument 2 has type ‘ulint’ constraints_parser.c: In function ‘ibrec_init_offsets_old’: constraints_parser.c:265: warning: format ‘%i’ expects type ‘int’, but argument 2 has type ‘ulint’ constraints_parser.c:288: warning: format ‘%i’ expects type ‘int’, but argument 2 has type ‘ulint’ constraints_parser.c: In function ‘check_for_a_record’: constraints_parser.c:320: warning: format ‘%lu’ expects type ‘long unsigned int’, but argument 3 has type ‘int’ constraints_parser.c:324: warning: format ‘%lu’ expects type ‘long unsigned int’, but argument 3 has type ‘int’ gcc -DHAVE_OFFSET64_T -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE=1 -D_LARGEFILE_SOURCE=1 -g -I include -I mysql-source/include -I mysql-source/innobase/include -o page_parser page_parser.c lib/tables_dict.o lib/libut.a page_parser.c: In function ‘process_ibpage’: page_parser.c:42: warning: format ‘%u’ expects type ‘unsigned int’, but argument 3 has type ‘time_t’ page_parser.c:46: warning: format ‘%u’ expects type ‘unsigned int’, but argument 3 has type ‘time_t’ page_parser.c: In function ‘process_ibfile’: page_parser.c:72: warning: format ‘%u’ expects type ‘unsigned int’, but argument 3 has type ‘time_t’ at first I ignored that but when i made the page_parser with my ibdata1 file and got all the pages whe i used the constrains_parsers i am getting empty rows totally empty or segmentation faul, do you know if the warning are causing the error, or what could i made wrong? Thanks in advance Alfredo Herrejon Hello I truncated a production table so I am in serious problems, i followed all the steps from the documentation at http://code.google.com/p/innodb-tools/wiki/InnodbRecoverySteps, but when I made the make command after the ./configure I got some warnings like

constraints_parser.c:88: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘ulint’
constraints_parser.c: In function ‘check_fields_sizes’:
constraints_parser.c:130: warning: format ‘%u’ expects type ‘unsigned int’, but argument 2 has type ‘ulint’
constraints_parser.c:144: warning: format ‘%u’ expects type ‘unsigned int’, but argument 2 has type ‘ulint’
constraints_parser.c:144: warning: format ‘%u’ expects type ‘unsigned int’, but argument 4 has type ‘ulint’
constraints_parser.c: In function ‘ibrec_init_offsets_new’:
constraints_parser.c:231: warning: format ‘%i’ expects type ‘int’, but argument 2 has type ‘ulint’
constraints_parser.c: In function ‘ibrec_init_offsets_old’:
constraints_parser.c:265: warning: format ‘%i’ expects type ‘int’, but argument 2 has type ‘ulint’
constraints_parser.c:288: warning: format ‘%i’ expects type ‘int’, but argument 2 has type ‘ulint’
constraints_parser.c: In function ‘check_for_a_record’:
constraints_parser.c:320: warning: format ‘%lu’ expects type ‘long unsigned int’, but argument 3 has type ‘int’
constraints_parser.c:324: warning: format ‘%lu’ expects type ‘long unsigned int’, but argument 3 has type ‘int’
gcc -DHAVE_OFFSET64_T -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE=1 -D_LARGEFILE_SOURCE=1 -g -I include -I mysql-source/include -I mysql-source/innobase/include -o page_parser page_parser.c lib/tables_dict.o lib/libut.a
page_parser.c: In function ‘process_ibpage’:
page_parser.c:42: warning: format ‘%u’ expects type ‘unsigned int’, but argument 3 has type ‘time_t’
page_parser.c:46: warning: format ‘%u’ expects type ‘unsigned int’, but argument 3 has type ‘time_t’
page_parser.c: In function ‘process_ibfile’:
page_parser.c:72: warning: format ‘%u’ expects type ‘unsigned int’, but argument 3 has type ‘time_t’

at first I ignored that but when i made the page_parser with my ibdata1 file and got all the pages whe i used the constrains_parsers i am getting empty rows totally empty or segmentation faul, do you know if the warning are causing the error, or what could i made wrong? Thanks in advance Alfredo Herrejon

]]> By: Alexey Kovyrin http://www.mysqlperformanceblog.com/2007/11/26/data-recovery-toolkit-for-innodb-version-01-released/comment-page-1/#comment-209035 Alexey Kovyrin Thu, 29 Nov 2007 22:37:04 +0000 http://www.mysqlperformanceblog.com/2007/11/26/data-recovery-toolkit-for-innodb-version-01-released/#comment-209035 Sheeri, Well, sometimes sh*t happens and it is nice to have such tool ready ;-) Sheeri,

Well, sometimes sh*t happens and it is nice to have such tool ready ;-)

]]> By: Sheeri Cabral http://www.mysqlperformanceblog.com/2007/11/26/data-recovery-toolkit-for-innodb-version-01-released/comment-page-1/#comment-209028 Sheeri Cabral Thu, 29 Nov 2007 22:23:27 +0000 http://www.mysqlperformanceblog.com/2007/11/26/data-recovery-toolkit-for-innodb-version-01-released/#comment-209028 I hope I never need this toolset, but I'm glad it's there! I hope I never need this toolset, but I’m glad it’s there!

]]> By: peter http://www.mysqlperformanceblog.com/2007/11/26/data-recovery-toolkit-for-innodb-version-01-released/comment-page-1/#comment-205273 peter Mon, 26 Nov 2007 21:46:38 +0000 http://www.mysqlperformanceblog.com/2007/11/26/data-recovery-toolkit-for-innodb-version-01-released/#comment-205273 Thank you Alexey for having it published. I should only note what "Undelete" and "Dropped Tables" is only one application of this toolset. FileSystem corruption or bad Innodb crashes are also possible applications. Thank you Alexey for having it published.

I should only note what “Undelete” and “Dropped Tables” is only one application of this toolset. FileSystem corruption or bad Innodb crashes are also possible applications.

]]> By: Sangy Simmons http://www.mysqlperformanceblog.com/2007/11/26/data-recovery-toolkit-for-innodb-version-01-released/comment-page-1/#comment-806492 Sangy Simmons Mon, 26 Nov 2007 07:00:01 +0000 http://www.mysqlperformanceblog.com/2007/11/26/data-recovery-toolkit-for-innodb-version-01-released/#comment-806492 <div class="item-body"><p>Recently my friend has lost his all MySQL data from the hard drive and he was very afraid. Without losing time he called me then I suggest him to try stellar database recovery software for the recovery of his deleted data. By this software he recovered his all deleted data, now this software become his one of favorite software for data recovery. The post is really helpful for the people like him.</p> <div class="clear"></div></div>

Recently my friend has lost his all MySQL data from the hard drive and he was very afraid. Without losing time he called me then I suggest him to try stellar database recovery software for the recovery of his deleted data. By this software he recovered his all deleted data, now this software become his one of favorite software for data recovery. The post is really helpful for the people like him.

]]>