Crash during prepare on xtrabackup_55 based on xtradb55

Bug #736582 reported by Vadim Tkachenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Fix Released
Critical
Alexey Kopytov

Bug Description

I am trying to prepare backup taken with xtrabackup_55 from branch xtrabackup-parallel-compression

Backup was taken as:
./xtrabackup_55 --backup --compress --compress-threads=24 --target-dir=/data/bench/xb/

I think crash is related to fact that xtrabackup scan only 16% of log up to log record 304315504227

the full log size is ~7500MB, but xtrabackup scans only from 303002624512 to 304315504227 , which is only 1200MB

./xtrabackup_55 --prepare --use-memory=100G --target-dir=/data/bench/xb/
./xtrabackup_55 Ver undefined Rev undefined for 5.5.9 Linux (x86_64)
xtrabackup: cd to /data/bench/xb/
xtrabackup: This target seems to be not prepared yet.
xtrabackup: xtrabackup_logfile detected: size=9203761152, start_lsn=(302997381657)
xtrabackup: Temporary instance for recovery is set as followings.
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:10M:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 1
xtrabackup: innodb_log_file_size = 9203761152
110316 13:38:39 InnoDB: Using Linux native AIO
xtrabackup: Starting InnoDB instance for recovery.
xtrabackup: Using 107374182400 bytes for buffer pool (set by --use-memory parameter)
110316 13:38:39 InnoDB: The InnoDB memory heap is disabled
110316 13:38:39 InnoDB: Mutexes and rw_locks use GCC atomic builtins
110316 13:38:39 InnoDB: Compressed tables use zlib 1.2.3
110316 13:38:39 InnoDB: Using Linux native AIO
110316 13:38:39 InnoDB: Warning: innodb_file_io_threads is deprecated. Please use innodb_read_io_threads and innodb_write_io_threads instead
110316 13:38:39 InnoDB: Initializing buffer pool, size = 100.0G
110316 13:38:49 InnoDB: Completed initialization of buffer pool
110316 13:38:49 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 302997381657
110316 13:38:51 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Doing recovery: scanned up to log sequence number 303002624512 (0 %)
InnoDB: Doing recovery: scanned up to log sequence number 303007867392 (0 %)
InnoDB: Doing recovery: scanned up to log sequence number 303013110272 (0 %)
InnoDB: Doing recovery: scanned up to log sequence number 303018353152 (0 %)
InnoDB: Doing recovery: scanned up to log sequence number 303023596032 (0 %)
InnoDB: Doing recovery: scanned up to log sequence number 303028838912 (0 %)
InnoDB: Doing recovery: scanned up to log sequence number 303034081792 (0 %)
InnoDB: Doing recovery: scanned up to log sequence number 303039324672 (0 %)
InnoDB: Doing recovery: scanned up to log sequence number 303044567552 (0 %)
InnoDB: Doing recovery: scanned up to log sequence number 303049810432 (0 %)
InnoDB: Doing recovery: scanned up to log sequence number 303055053312 (0 %)
InnoDB: Doing recovery: scanned up to log sequence number 303060296192 (0 %)
InnoDB: Doing recovery: scanned up to log sequence number 303065539072 (0 %)
InnoDB: Doing recovery: scanned up to log sequence number 303070781952 (0 %)
InnoDB: Doing recovery: scanned up to log sequence number 303076024832 (0 %)
InnoDB: Doing recovery: scanned up to log sequence number 303081267712 (1 %)
InnoDB: Doing recovery: scanned up to log sequence number 303086510592 (1 %)
InnoDB: Doing recovery: scanned up to log sequence number 303091753472 (1 %)
InnoDB: Doing recovery: scanned up to log sequence number 303096996352 (1 %)
InnoDB: Doing recovery: scanned up to log sequence number 303102239232 (1 %)
InnoDB: Doing recovery: scanned up to log sequence number 303107482112 (1 %)
InnoDB: Doing recovery: scanned up to log sequence number 303112724992 (1 %)
InnoDB: Doing recovery: scanned up to log sequence number 303117967872 (1 %)
InnoDB: Doing recovery: scanned up to log sequence number 303123210752 (1 %)
InnoDB: Doing recovery: scanned up to log sequence number 303128453632 (1 %)
InnoDB: Doing recovery: scanned up to log sequence number 303133696512 (1 %)
InnoDB: Doing recovery: scanned up to log sequence number 303138939392 (1 %)
InnoDB: Doing recovery: scanned up to log sequence number 303144182272 (1 %)
InnoDB: Doing recovery: scanned up to log sequence number 303149425152 (1 %)
InnoDB: Doing recovery: scanned up to log sequence number 303154668032 (1 %)
InnoDB: Doing recovery: scanned up to log sequence number 303159910912 (1 %)
InnoDB: Doing recovery: scanned up to log sequence number 303165153792 (2 %)
InnoDB: Doing recovery: scanned up to log sequence number 303170396672 (2 %)
InnoDB: Doing recovery: scanned up to log sequence number 303175639552 (2 %)
InnoDB: Doing recovery: scanned up to log sequence number 303180882432 (2 %)
InnoDB: Doing recovery: scanned up to log sequence number 303186125312 (2 %)
InnoDB: Doing recovery: scanned up to log sequence number 303191368192 (2 %)
InnoDB: Doing recovery: scanned up to log sequence number 303196611072 (2 %)
InnoDB: Doing recovery: scanned up to log sequence number 303201853952 (2 %)
InnoDB: Doing recovery: scanned up to log sequence number 303207096832 (2 %)
InnoDB: Doing recovery: scanned up to log sequence number 303212339712 (2 %)
InnoDB: Doing recovery: scanned up to log sequence number 303217582592 (2 %)
InnoDB: Doing recovery: scanned up to log sequence number 303222825472 (2 %)
InnoDB: Doing recovery: scanned up to log sequence number 303228068352 (2 %)
InnoDB: Doing recovery: scanned up to log sequence number 303233311232 (2 %)
InnoDB: Doing recovery: scanned up to log sequence number 303238554112 (2 %)
InnoDB: Doing recovery: scanned up to log sequence number 303243796992 (3 %)
InnoDB: Doing recovery: scanned up to log sequence number 303249039872 (3 %)
InnoDB: Doing recovery: scanned up to log sequence number 303254282752 (3 %)
InnoDB: Doing recovery: scanned up to log sequence number 303259525632 (3 %)
InnoDB: Doing recovery: scanned up to log sequence number 303264768512 (3 %)
InnoDB: Doing recovery: scanned up to log sequence number 303270011392 (3 %)
InnoDB: Doing recovery: scanned up to log sequence number 303275254272 (3 %)
InnoDB: Doing recovery: scanned up to log sequence number 303280497152 (3 %)
InnoDB: Doing recovery: scanned up to log sequence number 303285740032 (3 %)
InnoDB: Doing recovery: scanned up to log sequence number 303290982912 (3 %)
InnoDB: Doing recovery: scanned up to log sequence number 303296225792 (3 %)
InnoDB: Doing recovery: scanned up to log sequence number 303301468672 (3 %)
InnoDB: Doing recovery: scanned up to log sequence number 303306711552 (3 %)
InnoDB: Doing recovery: scanned up to log sequence number 303311954432 (3 %)
InnoDB: Doing recovery: scanned up to log sequence number 303317197312 (3 %)
InnoDB: Doing recovery: scanned up to log sequence number 303322440192 (3 %)
InnoDB: Doing recovery: scanned up to log sequence number 303327683072 (4 %)
InnoDB: Doing recovery: scanned up to log sequence number 303332925952 (4 %)
InnoDB: Doing recovery: scanned up to log sequence number 303338168832 (4 %)
InnoDB: Doing recovery: scanned up to log sequence number 303343411712 (4 %)
InnoDB: Doing recovery: scanned up to log sequence number 303348654592 (4 %)
InnoDB: Doing recovery: scanned up to log sequence number 303353897472 (4 %)
InnoDB: Doing recovery: scanned up to log sequence number 303359140352 (4 %)
InnoDB: Doing recovery: scanned up to log sequence number 303364383232 (4 %)
InnoDB: Doing recovery: scanned up to log sequence number 303369626112 (4 %)
InnoDB: Doing recovery: scanned up to log sequence number 303374868992 (4 %)
InnoDB: Doing recovery: scanned up to log sequence number 303380111872 (4 %)
InnoDB: Doing recovery: scanned up to log sequence number 303385354752 (4 %)
InnoDB: Doing recovery: scanned up to log sequence number 303390597632 (4 %)
InnoDB: Doing recovery: scanned up to log sequence number 303395840512 (4 %)
InnoDB: Doing recovery: scanned up to log sequence number 303401083392 (4 %)
InnoDB: Doing recovery: scanned up to log sequence number 303406326272 (4 %)
InnoDB: Doing recovery: scanned up to log sequence number 303411569152 (5 %)
InnoDB: Doing recovery: scanned up to log sequence number 303416812032 (5 %)
InnoDB: Doing recovery: scanned up to log sequence number 303422054912 (5 %)
InnoDB: Doing recovery: scanned up to log sequence number 303427297792 (5 %)
InnoDB: Doing recovery: scanned up to log sequence number 303432540672 (5 %)
InnoDB: Doing recovery: scanned up to log sequence number 303437783552 (5 %)
InnoDB: Doing recovery: scanned up to log sequence number 303443026432 (5 %)
InnoDB: Doing recovery: scanned up to log sequence number 303448269312 (5 %)
InnoDB: Doing recovery: scanned up to log sequence number 303453512192 (5 %)
InnoDB: Doing recovery: scanned up to log sequence number 303458755072 (5 %)
InnoDB: Doing recovery: scanned up to log sequence number 303463997952 (5 %)
InnoDB: Doing recovery: scanned up to log sequence number 303469240832 (5 %)
InnoDB: Doing recovery: scanned up to log sequence number 303474483712 (5 %)
InnoDB: Doing recovery: scanned up to log sequence number 303479726592 (5 %)
InnoDB: Doing recovery: scanned up to log sequence number 303484969472 (5 %)
InnoDB: Doing recovery: scanned up to log sequence number 303490212352 (6 %)
InnoDB: Doing recovery: scanned up to log sequence number 303495455232 (6 %)
InnoDB: Doing recovery: scanned up to log sequence number 303500698112 (6 %)
InnoDB: Doing recovery: scanned up to log sequence number 303505940992 (6 %)
InnoDB: Doing recovery: scanned up to log sequence number 303511183872 (6 %)
InnoDB: Doing recovery: scanned up to log sequence number 303516426752 (6 %)
InnoDB: Doing recovery: scanned up to log sequence number 303521669632 (6 %)
InnoDB: Doing recovery: scanned up to log sequence number 303526912512 (6 %)
InnoDB: Doing recovery: scanned up to log sequence number 303532155392 (6 %)
InnoDB: Doing recovery: scanned up to log sequence number 303537398272 (6 %)
InnoDB: Doing recovery: scanned up to log sequence number 303542641152 (6 %)
InnoDB: Doing recovery: scanned up to log sequence number 303547884032 (6 %)
InnoDB: Doing recovery: scanned up to log sequence number 303553126912 (6 %)
InnoDB: Doing recovery: scanned up to log sequence number 303558369792 (6 %)
InnoDB: Doing recovery: scanned up to log sequence number 303563612672 (6 %)
InnoDB: Doing recovery: scanned up to log sequence number 303568855552 (6 %)
InnoDB: Doing recovery: scanned up to log sequence number 303574098432 (7 %)
InnoDB: Doing recovery: scanned up to log sequence number 303579341312 (7 %)
InnoDB: Doing recovery: scanned up to log sequence number 303584584192 (7 %)
InnoDB: Doing recovery: scanned up to log sequence number 303589827072 (7 %)
InnoDB: Doing recovery: scanned up to log sequence number 303595069952 (7 %)
InnoDB: Doing recovery: scanned up to log sequence number 303600312832 (7 %)
InnoDB: Doing recovery: scanned up to log sequence number 303605555712 (7 %)
InnoDB: Doing recovery: scanned up to log sequence number 303610798592 (7 %)
InnoDB: Doing recovery: scanned up to log sequence number 303616041472 (7 %)
InnoDB: Doing recovery: scanned up to log sequence number 303621284352 (7 %)
InnoDB: Doing recovery: scanned up to log sequence number 303626527232 (7 %)
InnoDB: Doing recovery: scanned up to log sequence number 303631770112 (7 %)
InnoDB: Doing recovery: scanned up to log sequence number 303637012992 (7 %)
InnoDB: Doing recovery: scanned up to log sequence number 303642255872 (7 %)
InnoDB: Doing recovery: scanned up to log sequence number 303647498752 (7 %)
InnoDB: Doing recovery: scanned up to log sequence number 303652741632 (8 %)
InnoDB: Doing recovery: scanned up to log sequence number 303657984512 (8 %)
InnoDB: Doing recovery: scanned up to log sequence number 303663227392 (8 %)
InnoDB: Doing recovery: scanned up to log sequence number 303668470272 (8 %)
InnoDB: Doing recovery: scanned up to log sequence number 303673713152 (8 %)
InnoDB: Doing recovery: scanned up to log sequence number 303678956032 (8 %)
InnoDB: Doing recovery: scanned up to log sequence number 303684198912 (8 %)
InnoDB: Doing recovery: scanned up to log sequence number 303689441792 (8 %)
InnoDB: Doing recovery: scanned up to log sequence number 303694684672 (8 %)
InnoDB: Doing recovery: scanned up to log sequence number 303699927552 (8 %)
InnoDB: Doing recovery: scanned up to log sequence number 303705170432 (8 %)
InnoDB: Doing recovery: scanned up to log sequence number 303710413312 (8 %)
InnoDB: Doing recovery: scanned up to log sequence number 303715656192 (8 %)
InnoDB: Doing recovery: scanned up to log sequence number 303720899072 (8 %)
InnoDB: Doing recovery: scanned up to log sequence number 303726141952 (8 %)
InnoDB: Doing recovery: scanned up to log sequence number 303731384832 (8 %)
InnoDB: Doing recovery: scanned up to log sequence number 303736627712 (9 %)
InnoDB: Doing recovery: scanned up to log sequence number 303741870592 (9 %)
InnoDB: Doing recovery: scanned up to log sequence number 303747113472 (9 %)
InnoDB: Doing recovery: scanned up to log sequence number 303752356352 (9 %)
InnoDB: Doing recovery: scanned up to log sequence number 303757599232 (9 %)
InnoDB: Doing recovery: scanned up to log sequence number 303762842112 (9 %)
InnoDB: Doing recovery: scanned up to log sequence number 303768084992 (9 %)
InnoDB: Doing recovery: scanned up to log sequence number 303773327872 (9 %)
InnoDB: Doing recovery: scanned up to log sequence number 303778570752 (9 %)
InnoDB: Doing recovery: scanned up to log sequence number 303783813632 (9 %)
InnoDB: Doing recovery: scanned up to log sequence number 303789056512 (9 %)
InnoDB: Doing recovery: scanned up to log sequence number 303794299392 (9 %)
InnoDB: Doing recovery: scanned up to log sequence number 303799542272 (9 %)
InnoDB: Doing recovery: scanned up to log sequence number 303804785152 (9 %)
InnoDB: Doing recovery: scanned up to log sequence number 303810028032 (9 %)
InnoDB: Doing recovery: scanned up to log sequence number 303815270912 (9 %)
InnoDB: Doing recovery: scanned up to log sequence number 303820513792 (10 %)
InnoDB: Doing recovery: scanned up to log sequence number 303825756672 (10 %)
InnoDB: Doing recovery: scanned up to log sequence number 303830999552 (10 %)
InnoDB: Doing recovery: scanned up to log sequence number 303836242432 (10 %)
InnoDB: Doing recovery: scanned up to log sequence number 303841485312 (10 %)
InnoDB: Doing recovery: scanned up to log sequence number 303846728192 (10 %)
InnoDB: Doing recovery: scanned up to log sequence number 303851971072 (10 %)
InnoDB: Doing recovery: scanned up to log sequence number 303857213952 (10 %)
InnoDB: Doing recovery: scanned up to log sequence number 303862456832 (10 %)
InnoDB: Doing recovery: scanned up to log sequence number 303867699712 (10 %)
InnoDB: Doing recovery: scanned up to log sequence number 303872942592 (10 %)
InnoDB: Doing recovery: scanned up to log sequence number 303878185472 (10 %)
InnoDB: Doing recovery: scanned up to log sequence number 303883428352 (10 %)
InnoDB: Doing recovery: scanned up to log sequence number 303888671232 (10 %)
InnoDB: Doing recovery: scanned up to log sequence number 303893914112 (10 %)
InnoDB: Doing recovery: scanned up to log sequence number 303899156992 (11 %)
InnoDB: Doing recovery: scanned up to log sequence number 303904399872 (11 %)
InnoDB: Doing recovery: scanned up to log sequence number 303909642752 (11 %)
InnoDB: Doing recovery: scanned up to log sequence number 303914885632 (11 %)
InnoDB: Doing recovery: scanned up to log sequence number 303920128512 (11 %)
InnoDB: Doing recovery: scanned up to log sequence number 303925371392 (11 %)
InnoDB: Doing recovery: scanned up to log sequence number 303930614272 (11 %)
InnoDB: Doing recovery: scanned up to log sequence number 303935857152 (11 %)
InnoDB: Doing recovery: scanned up to log sequence number 303941100032 (11 %)
InnoDB: Doing recovery: scanned up to log sequence number 303946342912 (11 %)
InnoDB: Doing recovery: scanned up to log sequence number 303951585792 (11 %)
InnoDB: Doing recovery: scanned up to log sequence number 303956828672 (11 %)
InnoDB: Doing recovery: scanned up to log sequence number 303962071552 (11 %)
InnoDB: Doing recovery: scanned up to log sequence number 303967314432 (11 %)
InnoDB: Doing recovery: scanned up to log sequence number 303972557312 (11 %)
InnoDB: Doing recovery: scanned up to log sequence number 303977800192 (11 %)
InnoDB: Doing recovery: scanned up to log sequence number 303983043072 (12 %)
InnoDB: Doing recovery: scanned up to log sequence number 303988285952 (12 %)
InnoDB: Doing recovery: scanned up to log sequence number 303993528832 (12 %)
InnoDB: Doing recovery: scanned up to log sequence number 303998771712 (12 %)
InnoDB: Doing recovery: scanned up to log sequence number 304004014592 (12 %)
InnoDB: Doing recovery: scanned up to log sequence number 304009257472 (12 %)
InnoDB: Doing recovery: scanned up to log sequence number 304014500352 (12 %)
InnoDB: Doing recovery: scanned up to log sequence number 304019743232 (12 %)
InnoDB: Doing recovery: scanned up to log sequence number 304024986112 (12 %)
InnoDB: Doing recovery: scanned up to log sequence number 304030228992 (12 %)
InnoDB: Doing recovery: scanned up to log sequence number 304035471872 (12 %)
InnoDB: Doing recovery: scanned up to log sequence number 304040714752 (12 %)
InnoDB: Doing recovery: scanned up to log sequence number 304045957632 (12 %)
InnoDB: Doing recovery: scanned up to log sequence number 304051200512 (12 %)
InnoDB: Doing recovery: scanned up to log sequence number 304056443392 (12 %)
InnoDB: Doing recovery: scanned up to log sequence number 304061686272 (13 %)
InnoDB: Doing recovery: scanned up to log sequence number 304066929152 (13 %)
InnoDB: Doing recovery: scanned up to log sequence number 304072172032 (13 %)
InnoDB: Doing recovery: scanned up to log sequence number 304077414912 (13 %)
InnoDB: Doing recovery: scanned up to log sequence number 304082657792 (13 %)
InnoDB: Doing recovery: scanned up to log sequence number 304087900672 (13 %)
InnoDB: Doing recovery: scanned up to log sequence number 304093143552 (13 %)
InnoDB: Doing recovery: scanned up to log sequence number 304098386432 (13 %)
InnoDB: Doing recovery: scanned up to log sequence number 304103629312 (13 %)
InnoDB: Doing recovery: scanned up to log sequence number 304108872192 (13 %)
InnoDB: Doing recovery: scanned up to log sequence number 304114115072 (13 %)
InnoDB: Doing recovery: scanned up to log sequence number 304119357952 (13 %)
InnoDB: Doing recovery: scanned up to log sequence number 304124600832 (13 %)
InnoDB: Doing recovery: scanned up to log sequence number 304129843712 (13 %)
InnoDB: Doing recovery: scanned up to log sequence number 304135086592 (13 %)
InnoDB: Doing recovery: scanned up to log sequence number 304140329472 (13 %)
InnoDB: Doing recovery: scanned up to log sequence number 304145572352 (14 %)
InnoDB: Doing recovery: scanned up to log sequence number 304150815232 (14 %)
InnoDB: Doing recovery: scanned up to log sequence number 304156058112 (14 %)
InnoDB: Doing recovery: scanned up to log sequence number 304161300992 (14 %)
InnoDB: Doing recovery: scanned up to log sequence number 304166543872 (14 %)
InnoDB: Doing recovery: scanned up to log sequence number 304171786752 (14 %)
InnoDB: Doing recovery: scanned up to log sequence number 304177029632 (14 %)
InnoDB: Doing recovery: scanned up to log sequence number 304182272512 (14 %)
InnoDB: Doing recovery: scanned up to log sequence number 304187515392 (14 %)
InnoDB: Doing recovery: scanned up to log sequence number 304192758272 (14 %)
InnoDB: Doing recovery: scanned up to log sequence number 304198001152 (14 %)
InnoDB: Doing recovery: scanned up to log sequence number 304203244032 (14 %)
InnoDB: Doing recovery: scanned up to log sequence number 304208486912 (14 %)
InnoDB: Doing recovery: scanned up to log sequence number 304213729792 (14 %)
InnoDB: Doing recovery: scanned up to log sequence number 304218972672 (14 %)
InnoDB: Doing recovery: scanned up to log sequence number 304224215552 (14 %)
InnoDB: Doing recovery: scanned up to log sequence number 304229458432 (15 %)
InnoDB: Doing recovery: scanned up to log sequence number 304234701312 (15 %)
InnoDB: Doing recovery: scanned up to log sequence number 304239944192 (15 %)
InnoDB: Doing recovery: scanned up to log sequence number 304245187072 (15 %)
InnoDB: Doing recovery: scanned up to log sequence number 304250429952 (15 %)
InnoDB: Doing recovery: scanned up to log sequence number 304255672832 (15 %)
InnoDB: Doing recovery: scanned up to log sequence number 304260915712 (15 %)
InnoDB: Doing recovery: scanned up to log sequence number 304266158592 (15 %)
InnoDB: Doing recovery: scanned up to log sequence number 304271401472 (15 %)
InnoDB: Doing recovery: scanned up to log sequence number 304276644352 (15 %)
InnoDB: Doing recovery: scanned up to log sequence number 304281887232 (15 %)
InnoDB: Doing recovery: scanned up to log sequence number 304287130112 (15 %)
InnoDB: Doing recovery: scanned up to log sequence number 304292372992 (15 %)
InnoDB: Doing recovery: scanned up to log sequence number 304297615872 (15 %)
InnoDB: Doing recovery: scanned up to log sequence number 304302858752 (15 %)
InnoDB: Doing recovery: scanned up to log sequence number 304308101632 (16 %)
InnoDB: Doing recovery: scanned up to log sequence number 304313344512 (16 %)
InnoDB: Doing recovery: scanned up to log sequence number 304315504227 (16 %)
InnoDB: 38 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 388 row operations to undo
InnoDB: Trx id counter is EF800
110316 13:40:07 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 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 in background the rollback of uncommitted transactions
110316 13:46:16 InnoDB: Rolling back trx with id EF6F2, 2 rows to undo
110316 13:46:16 InnoDB: Waiting for the background threads to start

InnoDB: Rolling back of trx id EF6F2 completed
110316 13:46:16 InnoDB: Rolling back trx with id EF6F0, 2 rows to undo

InnoDB: Rolling back of trx id EF6F0 completed
110316 13:46:16 InnoDB: Rolling back trx with id EF6EE, 2 rows to undo

InnoDB: Rolling back of trx id EF6EE completed
110316 13:46:16 InnoDB: Rolling back trx with id EF6ED, 2 rows to undo

InnoDB: Rolling back of trx id EF6ED completed
110316 13:46:16 InnoDB: Rolling back trx with id EF6EB, 2 rows to undo

InnoDB: Rolling back of trx id EF6EB completed
110316 13:46:16 InnoDB: Rolling back trx with id EF6E9, 5 rows to undo

InnoDB: Rolling back of trx id EF6E9 completed
110316 13:46:16 InnoDB: Rolling back trx with id EF6E8, 2 rows to undo

InnoDB: Rolling back of trx id EF6E8 completed
110316 13:46:16 InnoDB: Rolling back trx with id EF6E7, 4 rows to undo

InnoDB: Rolling back of trx id EF6E7 completed
110316 13:46:16 InnoDB: Rolling back trx with id EF6E3, 3 rows to undo

InnoDB: Rolling back of trx id EF6E3 completed
110316 13:46:16 InnoDB: Rolling back trx with id EF6E1, 5 rows to undo
110316 13:46:16 InnoDB: Assertion failure in thread 140480148174608 in file /data/opt/vadim/xtrabackup-parallel-compression/Percona-Server-5.5/storage/innobase/btr/btr0cur.c line 300
InnoDB: Failing assertion: btr_page_get_prev(get_block->frame, mtr) == page_get_page_no(page)
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.

Related branches

Changed in percona-xtrabackup:
status: New → Triaged
importance: Undecided → Critical
assignee: nobody → Alexey Kopytov (akopytov)
milestone: none → 1.6
Revision history for this message
Vadim Tkachenko (vadim-tk) wrote :

I do not have this problem when I take backup with xtrabackup_55 from lp:~percona-dev/percona-xtrabackup/port-to-ps-5.5
branch. So I think it is related to xtrabackup-parallel-compression.

Changed in percona-xtrabackup:
milestone: 1.6 → none
Revision history for this message
Stewart Smith (stewart) wrote :

Alexey, what is the status of this bug? Am I correct in thinking that xtrabackup-parallel-compression isn't in trunk?

Revision history for this message
Alexey Kopytov (akopytov) wrote :

The status is In Progress. Correct, not in trunk.

Changed in percona-xtrabackup:
status: Triaged → In Progress
Stewart Smith (stewart)
Changed in percona-xtrabackup:
milestone: none → 1.7
Changed in percona-xtrabackup:
status: In Progress → Fix Committed
Stewart Smith (stewart)
Changed in percona-xtrabackup:
milestone: 1.9.0 → 1.9.1
Stewart Smith (stewart)
Changed in percona-xtrabackup:
status: Fix Committed → Fix Released
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-214

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.