Well, both innodb_log_file_size are commented out (on the Master and on the Slave). I
tried initially your 6G allocation, and it failed like this:
130718 10:27:36 InnoDB: Initializing buffer pool, size = 6.0G
InnoDB: mmap(6621757440 bytes) failed; errno 12
130718 10:27:36 InnoDB: Completed initialization of buffer pool
130718 10:27:36 InnoDB: Fatal error: cannot allocate memory for the buffer pool
xtrabackup: innodb_init(): Error occured.
So I removed the --use-memory=6G from the command line statement (to accept the default)
and it failed with that message I sent out earlier. I just tried using --use-memory=2G
and got a different error this time:
130718 10:38:39 InnoDB: Initializing buffer pool, size = 2.0G
130718 10:38:39 InnoDB: Completed initialization of buffer pool
130718 10:38:39 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 201164172631
130718 10:38:39 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 201165485500 (55 %)
130718 10:39:12 InnoDB: Assertion failure in thread 47059172530960 in file fsp0fsp.c line
InnoDB: Failing assertion: space != 0
So I'm closer, but what is "Failing assertion: space != 0"?
Systems Services Librarian
Vanderbilt University Library
From: Marcus Bointon [mailto:marcus@stripped]
Sent: Thursday, July 18, 2013 10:38 AM
To: McGranahan, Jamen
Subject: Re: 2 slaves - one Master; continues to fail
On 18 Jul 2013, at 17:29, "McGranahan, Jamen" <jamen.mcgranahan@stripped>
> So I followed your steps and here is what I get (when I try to do the --apply-log):
> 130718 10:28:02 InnoDB: Error: all log files must be created at the same time.
> 130718 10:28:02 InnoDB: All log files must be created also in database creation.
> 130718 10:28:02 InnoDB: If you want bigger or smaller log files, shut down the
> 130718 10:28:02 InnoDB: database and make sure there were no errors in shutdown.
> 130718 10:28:02 InnoDB: Then delete the existing log files. Edit the .cnf file
> 130718 10:28:02 InnoDB: and start the database again.
> xtrabackup: innodb_init(): Error occured.
> innobackupex: Error:
> innobackupex: ibbackup failed at /usr/bin/innobackupex line 389.
That sounds like your innodb_log_file_size in your slave's my.cnf is different from the
master you backed up from. They should really have almost-identical configs.
Alternatively, it may be that there's something amiss with your master (since xtrabackup
is only really copying the files) that's only showing up here.