InnoDB: failed with error 95 #1

jbergstroem · 2018-10-27T15:10:46Z

Money quote: InnoDB: preallocating 12582912 bytes for file ./ibdata1 failed with error 95

I've tried all "remedies" suggested to no avail:

innodb_flush_method = fsync
innodb_use_native_aio = false
lower_case_table_names = 2

A workaround is skipping innodb: docker -e SKIP_INNODB=1 ...

Upstream issues:

The text was updated successfully, but these errors were encountered:

jbergstroem · 2019-01-24T13:27:51Z

It looks like the only workaround for the moment is avoiding mount binds. I will update readme to reflect this.

jbergstroem · 2019-01-24T13:49:42Z

I've added additional documentation to suggest using volumes. For those who would end up from other parts of the Internet, do something like:

$ docker volume create db
db
$ docker run -it --rm --name=db \
         -v db:/var/lib/mysql \
         jbergstroem/mariadb-alpine

More info can be found here.

I will keep this open until I can verify that mount binds will work with upstream mariadb/mysql.

jbergstroem · 2020-02-02T01:25:29Z

So, in more recent versions of MariaDB I can't reproduce this any longer. Will keep open a bit longer; but I still think a best practice is to create a volume as part of your workflow.

Previous versions of MariaDB broke in certain scenarios when using docker, aufs or other mounted drives with Mariadb `10.2.x` and likely also some versions of `10.3.x`. Fixes: #1

ghost · 2020-08-11T21:48:34Z

Hey, I'm experiencing this again, also with SKIP_INNODB=1

jbergstroem · 2020-08-11T21:50:27Z

Hey, I'm experiencing this again, also with SKIP_INNODB=1

Hello! What version are you using? How are you starting it? Can you share all text output from docker? You should not be able to see an innodb-related error if you're skipping it.

ghost · 2020-08-12T16:13:45Z

Hey, I'm experiencing this again, also with SKIP_INNODB=1

Hello! What version are you using? How are you starting it? Can you share all text output from docker? You should not be able to see an innodb-related error if you're skipping it.

Somehow when I tried it again today to send you logs it went through.. So everything is running now.. Yes, SKIP_INNODB=1 was used

jbergstroem · 2020-08-12T21:16:14Z

Somehow when I tried it again today to send you logs it went through.. So everything is running now.. Yes, SKIP_INNODB=1 was used

Ok – good to hear. Feel free to open a new issue should you have more problems.

ghost · 2020-08-13T06:32:50Z

Thanks, however this InnoDB is broken problem persists.. It was just workaround.. You did not face this issue with latest build? I was running it on Debian 10.

jbergstroem · 2020-08-13T13:51:50Z

Thanks, however this InnoDB is broken problem persists.. It was just workaround.. You did not face this issue with latest build? I was running it on Debian 10.

I've tested on MacOS (my laptop) as well as running the test suite in github actions which runs Ubuntu 18.x. That should be a very similar environment to Debian 10 (glibc, kernel, packages, ..).

Can you provide me with the following and I will try to spin up a vm to test?

What is your debian version? ($ cat /etc/debian_version)
What is your docker version? ($ apt info docker-ce | head -n 2)
What filesystem do you use to store docker volume/data in? (ZFS is known to have shown these symptoms - check the link in the issue)
Provide output of: $ docker run -it jbergstroem/mariadb-alpine:10.4.13

Thanks!

jbergstroem · 2020-08-13T22:45:56Z

I found your issue here: firefly-iii/firefly-iii#3688

Did you try working around the allocation issue by creating a volume in your docker compose and assigning it to this container (see above)? Should work.

I have a todo to create some docker-compose.yml examples while refactoring documentation. Thanks for reminding me.

jbergstroem · 2020-08-13T23:20:36Z

Answering myself after testing on a Debian 10.5 with ZFS:

Did you try working around the allocation issue by creating a volume in your docker compose and assigning it to this container (see above)? Should work.

It doesn't work:

Creating jbergstroem_fireflyiiidb_1 ... done
Creating jbergstroem_fireflyiii_1   ... done
Attaching to jbergstroem_fireflyiiidb_1, jbergstroem_fireflyiii_1
fireflyiiidb_1  | 2020-08-13 23:16:35 0 [ERROR] InnoDB: preallocating 12582912 bytes for file ./ibdata1 failed with error 95
fireflyiiidb_1  | 2020-08-13 23:16:35 0 [ERROR] InnoDB: Could not set the file size of './ibdata1'. Probably out of disk space
fireflyiiidb_1  | 2020-08-13 23:16:35 0 [ERROR] InnoDB: Database creation was aborted with error Generic error. You may need to delete the ibdata1 file before trying to start up again.

Will compare to other alpines and see whats different; but last I dug into this, it was docker filesystem-related.

Edit: I have tried with yobasystems/alpine-mariadb which has the same issue.

ghost · 2020-08-14T13:26:25Z

Hey ! Sorry that I did not reply faster. I really appreciate your care, hopefully it will get fixed.

jbergstroem · 2020-08-15T15:30:38Z

Money quote here:

Fallocate doesnt work on some storage backends used for Containers (LXD, Docker...). In my Case it was ZFS.

I'll investigate switching to another base.

jbergstroem · 2020-09-20T13:38:25Z

For those who are interested, here's a fairly technical writeup on one way to handle fallocate on COW filesystems (such as ZFS): openzfs/zfs#326 (comment)

jbergstroem · 2020-09-27T14:26:54Z

If you are monitoring this thread for updates: there is now a test container that's built on glibc via rawhide. It took a while to get right since I am a) building from source and b) moving into a SCRATCH container.

jbergstroem · 2020-09-27T14:53:39Z

Here's output from my zfs machine. Summary: the new container works whereas the old (still) breaks.

$ docker run -it -v test:/var/lib/mysql jbergstroem/mariadb-alpine:test-rawhide-glibc
2020-09-27 14:50:03 0 [Note] /bin/mysqld (mysqld 10.4.14-MariaDB) starting as process 1 ...
2020-09-27 14:50:03 0 [Note] InnoDB: Using Linux native AIO
2020-09-27 14:50:03 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-27 14:50:03 0 [Note] InnoDB: Uses event mutexes
2020-09-27 14:50:03 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-27 14:50:03 0 [Note] InnoDB: Number of pools: 1
2020-09-27 14:50:03 0 [Note] InnoDB: Using SSE2 crc32 instructions
2020-09-27 14:50:03 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
2020-09-27 14:50:03 0 [Note] InnoDB: Initializing buffer pool, total size = 10M, instances = 1, chunk size = 10M
2020-09-27 14:50:03 0 [Note] InnoDB: Completed initialization of buffer pool
2020-09-27 14:50:03 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2020-09-27 14:50:03 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2020-09-27 14:50:03 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2020-09-27 14:50:03 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2020-09-27 14:50:03 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2020-09-27 14:50:03 0 [Note] InnoDB: Waiting for purge to start
2020-09-27 14:50:03 0 [Note] InnoDB: 10.4.14 started; log sequence number 60967; transaction id 21
2020-09-27 14:50:03 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2020-09-27 14:50:03 0 [Note] Plugin 'unix_socket' is disabled.
2020-09-27 14:50:03 0 [Note] InnoDB: Buffer pool(s) load completed at 200927 14:50:03
2020-09-27 14:50:03 0 [Note] Server socket created on IP: '::'.
2020-09-27 14:50:03 0 [Note] Reading of all Master_info entries succeeded
2020-09-27 14:50:03 0 [Note] Added new Master_info '' to hash table
2020-09-27 14:50:03 0 [Note] /bin/mysqld: ready for connections.
Version: '10.4.14-MariaDB'  socket: '/run/mysqld/mysqld.sock'  port: 3306  MariaDB Server
^C2020-09-27 14:50:19 0 [Note] /bin/mysqld (initiated by: unknown): Normal shutdown
2020-09-27 14:50:19 0 [Note] Event Scheduler: Purging the queue. 0 events
2020-09-27 14:50:19 0 [Note] InnoDB: FTS optimize thread exiting.
2020-09-27 14:50:19 0 [Note] InnoDB: Starting shutdown...
2020-09-27 14:50:19 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
2020-09-27 14:50:19 0 [Note] InnoDB: Instance 0, restricted to 156 pages due to innodb_buf_pool_dump_pct=25
2020-09-27 14:50:19 0 [Note] InnoDB: Buffer pool(s) dump completed at 200927 14:50:19
2020-09-27 14:50:20 0 [Note] InnoDB: Shutdown completed; log sequence number 60976; transaction id 22
2020-09-27 14:50:20 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2020-09-27 14:50:20 0 [Note] /bin/mysqld: Shutdown complete

$ docker run -it -v test2:/var/lib/mysql jbergstroem/mariadb-alpine:latest
2020-09-27 14:51:08 0 [ERROR] InnoDB: preallocating 12582912 bytes for file ./ibdata1 failed with error 95
2020-09-27 14:51:08 0 [ERROR] InnoDB: Could not set the file size of './ibdata1'. Probably out of disk space
2020-09-27 14:51:08 0 [ERROR] InnoDB: Database creation was aborted with error Generic error. You may need to delete the ibdata1 file before trying to start up again.
2020-09-27 14:51:09 0 [ERROR] Plugin 'InnoDB' init function returned error.
2020-09-27 14:51:09 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2020-09-27 14:51:09 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2020-09-27 14:51:09 0 [ERROR] Aborting
<snip>

svaroqui · 2021-01-04T15:36:49Z

Should be fixed on alpine see https://jira.mariadb.org/browse/MDEV-16015 can one provide feedback

jbergstroem · 2021-01-04T17:06:54Z

Should be fixed on alpine see https://jira.mariadb.org/browse/MDEV-16015 can one provide feedback

I noticed too! Thanks for the feedback - will try it (note: still not yet available through alpine 3.12 - so i have to build manually from their tree).

jbergstroem · 2021-05-12T18:52:39Z

This should be finally fixed as part of landing 10.4.18. Please test and reopen if so.

jbergstroem added the pending: upstream Issue is waiting for a third party to make progress label Oct 27, 2018

jbergstroem mentioned this issue Jan 24, 2019

Unable to clean start due to missing default mysql database caused by /usr/bin/ clean up #3

Closed

erseco mentioned this issue Apr 23, 2020

Removed VOLUME in Dockerfile #16

Closed

jbergstroem mentioned this issue Jun 21, 2020

test: check starting InnoDB without a volume #27

Merged

jbergstroem closed this as completed in #27 Jun 21, 2020

jbergstroem reopened this Aug 13, 2020

jbergstroem changed the title ~~10.2.15: InnoDB is broken~~ InnoDB: failed with error 95 Aug 13, 2020

jbergstroem added the type: bug Something isn't working as expected label Aug 13, 2020

jbergstroem mentioned this issue Jan 17, 2021

Move away from Alpine as container base #49

Closed

ostankin mentioned this issue Mar 20, 2021

The latest webhippie/mariadb (digest b5d8096de470) doesn't start on some machines dockhippie/mariadb#35

Closed

jbergstroem closed this as completed May 12, 2021

svasek mentioned this issue Jan 20, 2022

Updated mariadb to 10.6.4-r2 and alpine to 3.15 #107

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

InnoDB: failed with error 95 #1

InnoDB: failed with error 95 #1

jbergstroem commented Oct 27, 2018 •

edited

Loading

jbergstroem commented Jan 24, 2019

jbergstroem commented Jan 24, 2019

jbergstroem commented Feb 2, 2020

ghost commented Aug 11, 2020

jbergstroem commented Aug 11, 2020 •

edited

Loading

ghost commented Aug 12, 2020

jbergstroem commented Aug 12, 2020 •

edited

Loading

ghost commented Aug 13, 2020

jbergstroem commented Aug 13, 2020 •

edited

Loading

jbergstroem commented Aug 13, 2020

jbergstroem commented Aug 13, 2020 •

edited

Loading

ghost commented Aug 14, 2020

jbergstroem commented Aug 15, 2020

jbergstroem commented Sep 20, 2020 •

edited

Loading

jbergstroem commented Sep 27, 2020 •

edited

Loading

jbergstroem commented Sep 27, 2020

svaroqui commented Jan 4, 2021

jbergstroem commented Jan 4, 2021 •

edited

Loading

jbergstroem commented May 12, 2021

InnoDB: failed with error 95 #1

InnoDB: failed with error 95 #1

Comments

jbergstroem commented Oct 27, 2018 • edited Loading

jbergstroem commented Jan 24, 2019

jbergstroem commented Jan 24, 2019

jbergstroem commented Feb 2, 2020

ghost commented Aug 11, 2020

jbergstroem commented Aug 11, 2020 • edited Loading

ghost commented Aug 12, 2020

jbergstroem commented Aug 12, 2020 • edited Loading

ghost commented Aug 13, 2020

jbergstroem commented Aug 13, 2020 • edited Loading

jbergstroem commented Aug 13, 2020

jbergstroem commented Aug 13, 2020 • edited Loading

ghost commented Aug 14, 2020

jbergstroem commented Aug 15, 2020

jbergstroem commented Sep 20, 2020 • edited Loading

jbergstroem commented Sep 27, 2020 • edited Loading

jbergstroem commented Sep 27, 2020

svaroqui commented Jan 4, 2021

jbergstroem commented Jan 4, 2021 • edited Loading

jbergstroem commented May 12, 2021

jbergstroem commented Oct 27, 2018 •

edited

Loading

jbergstroem commented Aug 11, 2020 •

edited

Loading

jbergstroem commented Aug 12, 2020 •

edited

Loading

jbergstroem commented Aug 13, 2020 •

edited

Loading

jbergstroem commented Aug 13, 2020 •

edited

Loading

jbergstroem commented Sep 20, 2020 •

edited

Loading

jbergstroem commented Sep 27, 2020 •

edited

Loading

jbergstroem commented Jan 4, 2021 •

edited

Loading