MySQL Forums
Forum List  »  InnoDB

Re: Power failure and innodb
Posted by: Smita Vhatkar
Date: February 04, 2015 01:03PM

Sunny Bains Wrote:
-------------------------------------------------------
> The use case described is very unusual.
>
> 1. Is this running inside a VM?


No.


>
> 2. Are the transactions rolled back or the data
> lost?


Data loss ( data, which was inserted into DB and was in committed state 2 -3 days back).



> I realise that in the OP's description, it says
> rolled back after a clean shutdown. Did you see
> something like this?
>
> 2015-02-04T01:14:35.098012Z 0 [Note] InnoDB: Log
> scan progressed past the checkpoint lsn XXXXXXXX
> 2015-02-04T01:14:35.098045Z 0 [Note] InnoDB: Doing
> recovery: scanned up to log sequence number
> NNNNNN
> 2015-02-04T01:14:35.099240Z 0 [Note] InnoDB: Doing
> recovery: scanned up to log sequence number
> NNNNNN
> 2015-02-04T01:14:35.099261Z 0 [Note] InnoDB:
> Database was not shutdown normally!
> 2015-02-04T01:14:35.099277Z 0 [Note] InnoDB:
> Starting crash recovery.
> 2015-02-04T01:14:35.551491Z 0 [Note] InnoDB: 1
> transaction(s) which must be rolled back or
> cleaned up in total 7 row operations to undo
> 2015-02-04T01:14:35.551532Z 0 [Note] InnoDB: Trx
> id counter is XXXX
> 2015-02-04T01:14:35.699284Z 0 [Note] InnoDB:
> Starting in background the rollback of uncommitted
> transactions
> 2015-02-04T01:14:35.699344Z 0 [Note] InnoDB:
> Rolling back trx with id TTTT, 7 rows to undo
>
> Can you please post the error log


Unfortunately we have not yet seen any Transaction or assertion failure related error in the error logs.

PSB error log of the day when crash recovery happened.

2015-01-22 08:36:06 1848 [Note] Plugin 'FEDERATED' is disabled.
2015-01-22 08:36:06 1848 [Warning] option 'innodb-autoextend-increment': unsigned value 67108864 adjusted to 1000
2015-01-22 08:36:06 750 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-01-22 08:36:06 1848 [Note] InnoDB: The InnoDB memory heap is disabled
2015-01-22 08:36:06 1848 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-01-22 08:36:06 1848 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-01-22 08:36:06 1848 [Note] InnoDB: Not using CPU crc32 instructions
2015-01-22 08:36:06 1848 [Note] InnoDB: Initializing buffer pool, size = 114.0M
2015-01-22 08:36:06 1848 [Note] InnoDB: Completed initialization of buffer pool
2015-01-22 08:36:07 1848 [Note] InnoDB: Highest supported file format is Barracuda.
2015-01-22 08:36:08 1848 [Note] InnoDB: 128 rollback segment(s) are active.
2015-01-22 08:36:08 1848 [Note] InnoDB: Waiting for purge to start
2015-01-22 08:36:09 1848 [Note] InnoDB: 5.6.13 started; log sequence number 218251020
2015-01-22 08:36:10 1848 [Note] Server hostname (bind-address): '*'; port: 3306
2015-01-22 08:36:10 1848 [Note] IPv6 is available.
2015-01-22 08:36:10 1848 [Note] - '::' resolves to '::';
2015-01-22 08:36:10 1848 [Note] Server socket created on IP: '::'.
2015-01-22 08:36:12 1848 [Note] Event Scheduler: Loaded 0 events
2015-01-22 08:36:12 1848 [Note] C:/Program Files/MySQL/MySQL Server 5.6/bin\mysqld: ready for connections.
Version: '5.6.13' socket: '' port: 3306 MySQL Community Server (GPL)
2015-01-22 16:39:41 1808 [Note] Plugin 'FEDERATED' is disabled.
2015-01-22 16:39:41 1808 [Warning] option 'innodb-autoextend-increment': unsigned value 67108864 adjusted to 1000
2015-01-22 16:39:42 760 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-01-22 16:39:42 1808 [Note] InnoDB: The InnoDB memory heap is disabled
2015-01-22 16:39:42 1808 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-01-22 16:39:42 1808 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-01-22 16:39:42 1808 [Note] InnoDB: Not using CPU crc32 instructions
2015-01-22 16:39:42 1808 [Note] InnoDB: Initializing buffer pool, size = 114.0M
2015-01-22 16:39:42 1808 [Note] InnoDB: Completed initialization of buffer pool
2015-01-22 16:39:42 1808 [Note] InnoDB: Highest supported file format is Barracuda.
2015-01-22 16:39:43 1808 [Note] InnoDB: The log sequence numbers 218251020 and 218251020 in ibdata files do not match the log sequence number 218500159 in the ib_logfiles!
2015-01-22 16:39:43 1808 [Note] InnoDB: Database was not shutdown normally!
2015-01-22 16:39:43 1808 [Note] InnoDB: Starting crash recovery.
2015-01-22 16:39:43 1808 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-01-22 16:39:50 1808 [Note] InnoDB: Restoring possible half-written data pages
2015-01-22 16:39:50 1808 [Note] InnoDB: from the doublewrite buffer...
2015-01-22 16:39:53 1808 [Note] InnoDB: 128 rollback segment(s) are active.
2015-01-22 16:39:53 1808 [Note] InnoDB: Waiting for purge to start
2015-01-22 16:39:53 1808 [Note] InnoDB: 5.6.13 started; log sequence number 218500159
2015-01-22 16:39:53 1808 [Note] Server hostname (bind-address): '*'; port: 3306
2015-01-22 16:39:53 1808 [Note] IPv6 is available.
2015-01-22 16:39:53 1808 [Note] - '::' resolves to '::';
2015-01-22 16:39:53 1808 [Note] Server socket created on IP: '::'.
2015-01-22 16:39:53 1808 [Note] Event Scheduler: Loaded 0 events
2015-01-22 16:39:53 1808 [Note] C:/Program Files/MySQL/MySQL Server 5.6/bin\mysqld: ready for connections.
Version: '5.6.13' socket: '' port: 3306 MySQL Community Server (GPL)
2015-01-22 17:17:46 1800 [Note] Plugin 'FEDERATED' is disabled.
2015-01-22 17:17:46 1800 [Warning] option 'innodb-autoextend-increment': unsigned value 67108864 adjusted to 1000
2015-01-22 17:17:46 754 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-01-22 17:17:46 1800 [Note] InnoDB: The InnoDB memory heap is disabled
2015-01-22 17:17:46 1800 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-01-22 17:17:46 1800 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-01-22 17:17:47 1800 [Note] InnoDB: Not using CPU crc32 instructions
2015-01-22 17:17:47 1800 [Note] InnoDB: Initializing buffer pool, size = 114.0M
2015-01-22 17:17:47 1800 [Note] InnoDB: Completed initialization of buffer pool
2015-01-22 17:17:47 1800 [Note] InnoDB: Highest supported file format is Barracuda.
2015-01-22 17:17:48 1800 [Note] InnoDB: The log sequence numbers 218251020 and 218251020 in ibdata files do not match the log sequence number 218503589 in the ib_logfiles!
2015-01-22 17:17:48 1800 [Note] InnoDB: Database was not shutdown normally!
2015-01-22 17:17:48 1800 [Note] InnoDB: Starting crash recovery.
2015-01-22 17:17:48 1800 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-01-22 17:17:57 1800 [Note] InnoDB: Restoring possible half-written data pages
2015-01-22 17:17:57 1800 [Note] InnoDB: from the doublewrite buffer...
2015-01-22 17:17:58 1800 [Note] InnoDB: 128 rollback segment(s) are active.
2015-01-22 17:17:58 1800 [Note] InnoDB: Waiting for purge to start
2015-01-22 17:17:58 1800 [Note] InnoDB: 5.6.13 started; log sequence number 218503589
2015-01-22 17:17:58 1800 [Note] Server hostname (bind-address): '*'; port: 3306
2015-01-22 17:17:58 1800 [Note] IPv6 is available.
2015-01-22 17:17:58 1800 [Note] - '::' resolves to '::';
2015-01-22 17:17:58 1800 [Note] Server socket created on IP: '::'.
2015-01-22 17:17:58 1800 [Note] Event Scheduler: Loaded 0 events
2015-01-22 17:17:58 1800 [Note] C:/Program Files/MySQL/MySQL Server 5.6/bin\mysqld: ready for connections.
Version: '5.6.13' socket: '' port: 3306 MySQL Community Server (GPL)
2015-01-23 00:01:08 1800 [Note] C:/Program Files/MySQL/MySQL Server 5.6/bin\mysqld: Normal shutdown

Options: ReplyQuote


Subject
Views
Written By
Posted
8133
January 27, 2014 09:45AM
2715
January 28, 2014 08:42AM
2758
February 24, 2014 06:21AM
2213
March 05, 2014 08:15AM
2069
March 05, 2014 10:42PM
1934
March 07, 2014 07:46AM
1436
February 02, 2015 09:33AM
1411
February 02, 2015 11:43AM
1518
February 03, 2015 05:09AM
1469
February 03, 2015 07:04PM
Re: Power failure and innodb
1887
February 04, 2015 01:03PM
1158
June 04, 2015 07:35AM
2588
March 31, 2014 06:16AM
1453
March 18, 2015 11:12AM


Sorry, you can't reply to this topic. It has been closed.

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.