Asif, ----- Original Message ----- From: "Asif Iqbal" <[EMAIL PROTECTED]> Newsgroups: mailing.database.mysql Sent: Thursday, July 31, 2003 10:41 PM Subject: Mysqld is keep crashing
> > > This is what I bumped into now > > 030731 15:39:50 mysqld started > 030731 15:39:52 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 3491794745 > InnoDB: Doing recovery: scanned up to log sequence number 0 3491800490 > InnoDB: 1 transaction(s) which must be rolled back or cleaned up > InnoDB: in total 32 row operations to undo > InnoDB: Trx id counter is 0 3532544 > 030731 15:39:53 InnoDB: Starting an apply batch of log records to the > database... > InnoDB: Progress in percents: 7 8 9 10 11 12 13 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: Starting rollback of uncommitted transactions > InnoDB: Rolling back trx with id 0 3532191, 32 rows to undoInnoDB: Error: trying > to access page number 2650767236 in space 0 > InnoDB: which is outside the tablespace bounds. > InnoDB: Byte offset 0, len 16384, i/o type 10 > 030731 15:39:59 InnoDB: Assertion failure in thread 1 in file fil0fil.c line > 1176 > InnoDB: Failing assertion: 0 > InnoDB: We intentionally generate a memory trap. > InnoDB: Send a detailed bug report to [EMAIL PROTECTED] > mysqld got signal 11; > This could be because you hit a bug. It is also possible that this binary > or one of the libraries it was linked against is corrupt, improperly built, > or misconfigured. This error can also be caused by malfunctioning hardware. > We will try our best to scrape up some info that will hopefully help diagnose > the problem, but since we have already crashed, something is definitely wrong > and this may fail. > > key_buffer_size=402653184 > read_buffer_size=2093056 > 030731 15:39:59 mysqld ended > > > Anyone would know how I can fix it your InnoDB database is now corrupt. That may be a result of mixing ibdata files or ib_logfiles. I recall you were trying to modify my.cnf 2 days ago and had some problems. You can try starting with http://www.innodb.com/ibman.html#Forcing_recovery: set-variable = innodb_force_recovery = 4 and dump your tables and recreate your ibdata files and ib_logfiles. > I am using my-huge.cnf . I have 4 450Mhz with 4 gig ram > -- > Asif Iqbal Best regards, Heikki Tuuri Innobase Oy http://www.innodb.com Transactions, foreign keys, and a hot backup tool for MySQL Order MySQL technical support from https://order.mysql.com/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
