← Back to team overview

percona-discussion team mailing list archive

[Bug 372017] Re: unable to find free blocks from buffer pool with --use-memory if KB/MB/GB not specified


It is not a bug, you just are trying to start InnoDB with 1000 bytes
buffer pool. It never will work.

** Changed in: percona-xtrabackup
       Status: New => Won't Fix

unable to find free blocks from buffer pool with --use-memory if KB/MB/GB not specified
You received this bug notification because you are a member of Percona
developers, which is the registrant for Percona-XtraBackup.

Status in Open source backup tool for InnoDB and XtraDB: Won't Fix

Bug description:
I don't know if this constitutes as a "bug" or not ... but when i don't specify the units with --use-memory then it says it's unable to find free blocks...

This is innobackupex-1.5.1 w/xtrabackup 0.6

When I run:
innobackupex --apply-log --use-memory=1000 /data/mysql

It gives me:

090504 20:45:16  innobackupex: Starting ibbackup with command: xtrabackup --prepare --target-dir=/data/mysql --use-memory=1000

Warning: option 'use-memory': signed value 1000 adjusted to 1048576
xtrabackup  Ver beta-0.6 for 5.0.77 unknown-linux-gnu (x86_64)
xtrabackup: cd to /data/mysql
xtrabackup: This target seems to be not prepared yet.
090504 20:45:16  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
xtrabackup: Warning: cannot open ./xtrabackup_logfile. will try to find.
  xtrabackup: 'ib_logfile0' seems to be 'xtrabackup_logfile'. will retry.
xtrabackup: xtrabackup_logfile detected: size=5853773824, start_lsn=(175 3799303358)
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 = 5853773824
xtrabackup: Starting InnoDB instance for recovery.
xtrabackup: Using 1048576 bytes for buffer pool (set by --use-memory parameter)
InnoDB: Log scan progressed past the checkpoint lsn 175 3799303358
090504 20:45:17  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...
090504 20:45:27InnoDB: Warning: difficult to find free blocks from
InnoDB: the buffer pool (31 search iterations)! Consider
InnoDB: increasing the buffer pool size.
InnoDB: It is also possible that in your Unix version
InnoDB: fsync is very slow, or completely frozen inside
InnoDB: the OS kernel. Then upgrading to a newer version
InnoDB: of your operating system may help. Look at the
InnoDB: number of fsyncs in diagnostic info below.
InnoDB: Pending flushes (fsync) log: 0; buffer pool: 0
InnoDB: 151 OS file reads, 312 OS file writes, 0 OS fsyncs
InnoDB: Starting InnoDB Monitor to print further
InnoDB: diagnostics to the standard output.

if I have --use-memory=1000(M|G) then it works fine.