Project: datamanagement
Issue DM-5148: IN2P3 cluster worker nodes failed to start due to Innodb error
Next error happens when starting mariadb on worker (with existing data from 35TB dataset, which were generated by mysql): {code:bash} 2016-02-13 22:02:36 139632684558144 [Note] InnoDB: Completed initialization of buffer pool 2016-02-13 22:02:36 139632684558144 [ERROR] InnoDB: auto-extending data file ./ibdata1 is of a different size 640 pages (rounded down to MB) than specified in the .cnf file: initial 768 pages, max 0 (relevant if non-zero) pages! 2016-02-13 22:02:36 139632684558144 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data! 2016-02-13 22:02:36 139632684558144 [ERROR] Plugin 'InnoDB' init function returned error. 2016-02-13 22:02:36 139632684558144 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2016-02-13 22:02:36 139632684558144 [Note] Plugin 'FEEDBACK' is disabled. 2016-02-13 22:02:36 139632684558144 [ERROR] Unknown/unsupported storage engine: InnoDB 2016-02-13 22:02:36 139632684558144 [ERROR] Aborting {code}
Story points: 4