Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix running addon when using zfs as backing storage #21

Merged
merged 1 commit into from
Dec 6, 2019

Conversation

mjrider
Copy link
Contributor

@mjrider mjrider commented Jun 10, 2019

Proposed Changes

Drop innodb support

Short story, when using zfs and bind mounts for volumes innodb craps out on creating the ibdata1 file
Because i didn't find any usage of innodb, i think the easiest solution is just disabling i

Related Issues

https://bugs.alpinelinux.org/issues/9046

Redmine

https://jira.mariadb.org/browse/MDEV-16015

@addons-assistant
Copy link

💖 Thanks for opening this pull request! 💖 If your PR gets accepted and merged in, we will invite you to the project 🎉

@frenck
Copy link
Member

frenck commented Dec 6, 2019

Let's do it!

@frenck frenck merged commit 741d758 into hassio-addons:master Dec 6, 2019
@addons-assistant
Copy link

Congrats on merging your first pull request! 🎉🎉🎉

@gleepwurp
Copy link

Was this merge included in the dockerimage cut 8 days ago? (0.3.1). I'm having the same issue, and it looks like the image still tries to create INNODB files:

`Add-on version: 0.3.1
You are running the latest version of this add-on.
System: Ubuntu 19.10 (amd64 / qemux86-64)
Home Assistant version: 0.103.0
Supervisor version: 192
<--SNIP-->
cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] mysql.sh: executing...
[20:58:40] INFO: Initializing database...
Installing MariaDB/MySQL system tables in '/data/mysql' ...
2019-12-17 20:58:40 0 [ERROR] InnoDB: preallocating 12582912 bytes for file ./ibdata1 failed with error 95
2019-12-17 20:58:40 0 [ERROR] InnoDB: Could not set the file size of './ibdata1'. Probably out of disk space
2019-12-17 20:58:40 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.
2019-12-17 20:58:40 0 [ERROR] Plugin 'InnoDB' init function returned error.
2019-12-17 20:58:40 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2019-12-17 20:58:41 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2019-12-17 20:58:41 0 [ERROR] Aborting

`

Thanks!

@mjrider mjrider deleted the Fix-innodb-startup-issue branch December 18, 2019 08:05
@frenck
Copy link
Member

frenck commented Dec 18, 2019

It has been reverted and cannot be done.
At this point, I can only say that we are unable to support that setup.

@gleepwurp
Copy link

Understood, thank you for the clarification!

Maybe we can change the mysql backend requirement like was done with BitwardenRS... (see I listened to your latest podcast! ;) )

I'll check if that is feasible.

Thx,

G,

@gleepwurp
Copy link

I think this Pull request in nginx-proxy-manager might be fixing our issue with running docker on zfs, by implementing an SQLite version (or db-selectable at least):

NginxProxyManager/nginx-proxy-manager#256

We'll just have to wait a bit.

G.

@addons-assistant
Copy link

This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.

@addons-assistant addons-assistant bot locked as resolved and limited conversation to collaborators Jan 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants