Announcement

Announcement Module
Collapse
No announcement yet.

InnoDB: Error number 75 means 'Value too large for defined data type'

Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • InnoDB: Error number 75 means 'Value too large for defined data type'

    Hello,

    First of all, thanks for the tools and help you are providing to the community.

    I have ran into some problems using the innobackupex/xtrabackup script, although it may just be caused by the InnoDB binaries.

    I have the following error:


    InnoDB: Error number 75 means 'Value too large for defined data type'.InnoDB: Some operating system error numbers are described atInnoDB: http://dev.mysql.com/doc/refman/5.1/en/operating-system-error-codes.htmlInnoDB: File name ./my_database/my_big_table.ibdInnoDB: File operation call: 'stat'.InnoDB: Error: os_file_readdir_next_file() returned -1 inInnoDB: directory ./my_databaseInnoDB: Crash recovery may have failed for some .ibd files!


    This error happens when I am running the script in streaming and non-streaming modes. In streaming mode, the data for the table my_big_table.idb is copied but in non-streaming mode, the table data is not copied.

    The table size is currently about 5 GB. I am running an amazon AMI 2.6.35.14-95.38.amzn1.i686 and MySQL 5.1.52-1.6.amzn1. This is an EC2 small instance with ext3-formatted persistent storage.

    Would you have any idea what could be the cause? Technically I can still use the streaming mode, as it seems to work, but I would like to understand why this is happening, but also, why is the streaming mode working although the error is fired in both cases.

    Thanks
    Pierre

    Full Log:

    120120 07:45:01 innobackupex: Starting ibbackup with command: xtrabackup_51 --backup --suspend-at-end --log-stream --target-dir=./innobackupex: Waiting for ibbackup (pid=14660) to suspendinnobackupex: Suspend file '/media/ephemeral0/mysql/xtrabackup_suspended'xtrabackup: suspend-at-end is enabled.xtrabackup: uses posix_fadvise().xtrabackup: cd to /media/ephemeral0/mysqlxtrabackup: Target instance is assumed as followings.xtrabackup: innodb_data_home_dir = ./xtrabackup: innodb_data_file_path = ibdata1:10M:autoextendxtrabackup: innodb_log_group_home_dir = ./xtrabackup: innodb_log_files_in_group = 2xtrabackup: innodb_log_file_size = 268435456120120 7:45:01 InnoDB: Operating system error number 75 in a file operation.InnoDB: Error number 75 means 'Value too large for defined data type'.InnoDB: Some operating system error numbers are described atInnoDB: http://dev.mysql.com/doc/refman/5.1/en/operating-system-error-codes.htmlInnoDB: File name ./my_database/my_big_table.ibdInnoDB: File operation call: 'stat'.InnoDB: Error: os_file_readdir_next_file() returned -1 inInnoDB: directory ./my_databaseInnoDB: Crash recovery may have failed for some .ibd files! xtrabackup: Stream mode.>> log scanned up to (3 2936881750)120120 07:45:03 innobackupex: Continuing after ibbackup has suspendedinnobackupex: Starting to backup InnoDB tables and indexesinnobackupex: from original InnoDB data directory '/media/ephemeral0/mysql'innobackupex: Backing up as tar stream 'ibdata1'>> log scanned up to (3 2936977751)[.....]>> log scanned up to (3 2938381819)innobackupex: Backing up file '/media/ephemeral0/mysql/my_database/my_big_table.ibd'>> log scanned up to (3 2938473272)[.....]120120 07:53:56 innobackupex: Starting mysql with options: --password=xxxxxxxx --user='root' --unbuffered --120120 07:53:56 innobackupex: Connected to database with mysql child process (pid=14677)120120 07:53:58 innobackupex: Starting to lock all tables...>> log scanned up to (3 2946303833)>> log scanned up to (3 2946348808)120120 07:54:08 innobackupex: All tables locked and flushed to disk120120 07:54:08 innobackupex: Starting to backup .frm, .MRG, .MYD, .MYI,innobackupex: .TRG, .TRN, .ARM, .ARZ, .CSM, .CSV and .opt files ininnobackupex: subdirectories of '/media/ephemeral0/mysql'innobackupex: Backing up files '/media/ephemeral0/mysql/my_database/*.{frm,MYD,MYI,MRG,TRG,TRN,ARM,ARZ,CSM,CSV,opt,par }' (26 files)>> log scanned up to (3 2946353179)innobackupex: Backing up files '/media/ephemeral0/mysql/mysql/*.{frm,MYD,MYI,MRG,TRG,TRN,ARM,ARZ,CSM,CSV,opt,par }' (69 files)120120 07:54:10 innobackupex: Finished backing up .frm, .MRG, .MYD, .MYI, .TRG, .TRN, .ARM, .ARZ, .CSV, .CSM and .opt filesinnobackupex: Resuming ibbackupxtrabackup: The latest check point (for incremental): '3:2935060917'>> log scanned up to (3 2946354134)xtrabackup: Transaction log of lsn (3 2929484088) to (3 2946354134) was copied.120120 07:54:13 innobackupex: All tables unlocked120120 07:54:13 innobackupex: Connection to database server closedinnobackupex: Backup created in directory '/media/ephemeral0/tmp'innobackupex: MySQL binlog position: filename '', positioninnobackupex: You must use -i (--ignore-zeros) option for extraction of the tar stream.120120 07:54:13 innobackupex: completed OK!

  • #2
    This is probably a bug that should be filed on the Launchpad bug tracker.

    Comment

    Working...
    X