Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Not a Bug
-
10.5.7
-
None
-
Windows docker container only. Not Linux, not windows native
Description
From: https://github.com/docker-library/mariadb/issues/331
Run docker-compose up -d
connect with your favorite client (I'm using DBeaver Enterprise)
Run a create table statement:
CREATE TABLE NewTable (
ID int primary key,
name varchar(10)
)
Run a RENAME table statement like this:
RENAME TABLE mytestdb.NewTable TO mytestdb.NewTablea;
Then, run again, another RENAME the statement:
RENAME TABLE mytestdb.NewTablea TO mytestdb.NewTableb;
The error I'm getting is:
SQL Error [1025] [HY000]: (conn=4) Error on rename of './mytestdb/newtablea' to './mytestdb/newtableb' (errno: 194 "Tablespace is missing for a table")
Notes:
1 - When I install the MariaDB client via .msi installer for windows, all works fine
2 - I changed the variable lower_case_table_names to 1 because the default with windows is coming 2 for me, but with no success, the error still the same.
3 - I created the same container with mysql:latest image instead of mariadb and all works fine
4 - Tried to adjust folder permissions on windows, giving all permisions to anyone (like a chmod 777 on linux), but the erros still the same.
So I think that there's some problem with windows + mariadb:latest image
Attachments
Issue Links
- duplicates
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-
- relates to
-
-
- Closed
-
-
-
- Closed
-
- links to
Activity
if so, maybe danblack can reopen https://github.com/microsoft/WSL/issues/8443 . it still remains a "not MariaDB bug"
We had a user reproduce this issue on Win10 Pro 22H2, Docker Desktop + WSL2, MariaDB 1:11.2.2+maria~ubu2204, that is a migration failed with
pymysql.err.OperationalError: (1025, 'Error on rename of \'./darkflame/accounts\' to \'./darkflame/#sql-backup-1-20\' (errno: 194 "Tablespace is missing for a table")')
|
with a MariaDB log of
[ERROR] InnoDB: Cannot rename './darkflame/accounts.ibd' to './darkflame/#sql-backup-1-20.ibd' because the source file does not exist.
|
I'm commenting about it because the user reported that the reproducer in https://github.com/microsoft/WSL/issues/8443#issuecomment-1836812926 did not print any sort of "error on fstat errno 2", so while I think this it's still possible that MariaDB triggers some weird behaviour in 9P on Windows 10, it may be too quick to dismiss it as WSL#8443 and "not a MariaDB bug".
Hi Xiphoseer,
Sorry to here we've still got a new form of this. To validate the system calls used:
- install strace in the container (new container with "FROM mariadb:11.2.2\nRUN apt-get update && apt-get install -y strace")
- after initializing some data, before the rename, --user mysql --entrypoint "strace -s 99" --command mariadbd, then preform the rename. Like what wlad did above, use ProcessMonitor to cature the rename at the same time.
- yes I'm the user that put the broken reproducer. I was missing while doing the tests, and it didn't show up even though it looks exactly like the strace conditions, nor the under the basic rename. If you can create a C file and create a reproducer image that works in your environment that would be much appreciated.
Dockerfile
ARG VERSION=22.04FROM ubuntu:$VERSIONCOPY wsl8443.c .RUN apt-get update && apt-get install -y gcc strace && rm -rf /var/lib/apt/lists/*RUN gcc -o wsl8443 wsl8443.c
Hi! Unfortunatelly, I don't have the environment anymore, neither the laptop. Since I started to have slowing down problems to work with docker on WSL, I decided to migrate to a real Linux environment. Sorry, but thanks for all the effort!