Bug #34979 Signal 11 when trying to use ZFS Snapshot
| Submitted: | 2 Mar 2008 2:18 | Modified: | 2 Mar 2008 5:33 |
|---|---|---|---|
| Reporter: | Justin SB | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S1 (Critical) |
| Version: | 5.1.22-rc | OS: | Solaris |
| Assigned to: | CPU Architecture: | Any |
[2 Mar 2008 2:18]
Justin SB
[2 Mar 2008 5:33]
Justin SB
Actually, this was an error I made - I didn't bring down the ibdata1 file, and possibly some other files also weren't correctly in place. Although crashing with a signal 11 is probably slightly over the top, once I had a consistent copy of all the files everything was fine. I hope this helps others encountering the same problem.
[2 Feb 2009 11:26]
Maciek Gabryszak
Hello. uname -a SunOS 5.10 Generic_138889-02 i86pc i386 i86pc + mysql 5.1.30-GA when I take the snapshot from anothe mahine in log view: 090202 12:04:03 [Note] Event Scheduler: Killing the scheduler thread, thread id 1 090202 12:04:03 [Note] Event Scheduler: Waiting for the scheduler thread to reply 090202 12:04:03 [Note] Event Scheduler: Stopped 090202 12:04:03 [Note] Event Scheduler: Purging the queue. 1 events 090202 12:07:38 mysqld_safe Starting mysqld daemon with databases from /export/sql InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 090202 12:07:41 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Transaction 0 279239639 was in the XA prepared state. InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 0 row operations to undo InnoDB: Trx id counter is 0 279240448 InnoDB: Last MySQL binlog file position 0 162839326, file name /export/home/sql/log/master-szukaj-bin.000003 InnoDB: Starting in background the rollback of uncommitted transactions 090202 12:07:42 InnoDB: Rollback of non-prepared transactions completed 090202 12:07:42 InnoDB: Started; log sequence number 10 3298493006 090202 12:07:42 InnoDB: Starting recovery for XA transactions... 090202 12:07:42 InnoDB: Transaction 0 279239639 in prepared state after recovery 090202 12:07:42 InnoDB: Transaction contains changes to 1 rows 090202 12:07:42 InnoDB: 1 transactions in prepared state after recovery 090202 12:07:42 [Note] Found 1 prepared transaction(s) in InnoDB 090202 12:07:42 [Warning] Found 1 prepared XA transactions 090202 12:07:42 [Note] Event Scheduler: Loaded 1 event 090202 12:07:42 [Note] /opt/mysql/mysql/bin/mysqld: ready for connections. Version: '5.1.30-log' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL) 090202 12:07:42 [Note] Event Scheduler: scheduler thread started with id 1 I can't change data in innodb tables. I can't shutdown this database. I must kill -9 processes but when I try start and view this error again.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.050 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.