On Thu, May 06, 2004 at 09:55:30AM +1000, Daniel Kasak wrote: > Hi all. > > My boss just pulled the power on our MySQL server. > Yes, I've already thanked him. > > It's a 4.0.18 server, with MyISAM tables and InnoDB tables, running on a > 2.6.5 kernel and XFS filesystem. > > The XFS recovery proceeded without any complaints. > The InnoDB recovery also seemed to go smoothly ( great work by the way ): > > 040506 9:38:41 InnoDB: Database was not shut down normally. > InnoDB: Starting recovery from log files... > InnoDB: Starting log scan based on checkpoint at > InnoDB: log sequence number 0 1032429395 > InnoDB: Doing recovery: scanned up to log sequence number 0 1032430197 > 040506 9:38:42 InnoDB: Starting an apply batch of log records to the > database... > InnoDB: Progress in percents: 14 15 16 17 18 19 20 21 22 23 24 25 26 27 > 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 > 52 53 > 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 > 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 > InnoDB: Apply batch completed > InnoDB: Last MySQL binlog file position 0 139443, file name > ./screamer-bin.210 > 040506 9:38:42 InnoDB: Flushing modified pages from the buffer pool... > 040506 9:38:42 InnoDB: Started > > I've done a 'myisamchk' on all the MyISAM tables. They were all OK. > > My question is: should I trust my data now?
Yes. InnoDB is fully ACID compliant. > So anyway, should I bother with a restore? What's the chance of having > data corrupted / missing after a power 'failure' and recovery as above? The only "missing" data should be uncommitted transactions unless you've changed InnoDB's default flushing frequency. Jeremy -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! <[EMAIL PROTECTED]> | http://jeremy.zawodny.com/ [book] High Performance MySQL -- http://highperformancemysql.com/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
