Otto, et al,
I took a fresh look at this bug and it is fixed in the following live
images now:
* debian-live-12.10.0-amd64-gnome.iso
* debian-live-testing-amd64-gnome.iso (May 5, 2025)
Unfortunately, I do not know when it was fixed.
I think this bug was not in mariadb, but actually in linux-
Package: mariadb-server
Version: 1:10.11.3-1
Followup-For: Bug #1009290
X-Debbugs-Cc: witold.bary...@gmail.com
Just wwitching to fsync, does not appear to solve the problem either:
root@debian:~# cat /etc/mysql/mariadb.conf.d/90-live.cnf
[mysqld]
innodb_flush_method = fsync
root@debian:~#
Jun
Package: mariadb-server
Version: 1:10.11.3-1
Followup-For: Bug #1009290
X-Debbugs-Cc: witold.bary...@gmail.com
Still broken in 10.11.3.
This is fresh installation, zero modifications.
Jun 24 19:14:24 debian systemd[1]: Starting mariadb.service - MariaDB 10.11.3
database server...
Jun 24 19:14:
Hi,
I've faced same problem on a fresh Bookworm live system (mariadb-server
1:10.11.2-1).
As a workaround I've mounted /var/lib/mysql as a ext4 filesystem.
FYI: It works fine on Bullseye.
Kind regards,
--
Antoni Villalonga
https://friki.cat/
> How about temporarily inserting something like the implementation below of
> Arnaud R's workaround somewhere (where?) in mariadb-server(-10.6).postinst?
>
> Thank you!
> Daniel Lewart
> Urbana, Illinois
> ---
> # Temporary workaround which should be removed after upstream fixes
> # https://jira.m
Otto, et al,
How about temporarily inserting something like the implementation below of
Arnaud R's workaround somewhere (where?) in mariadb-server(-10.6).postinst?
Thank you!
Daniel Lewart
Urbana, Illinois
---
# Temporary workaround which should be removed after upstream fixes
# https://jira.mari
Otto, et al,
> I don't see anything new in upstream
> https://jira.mariadb.org/browse/MDEV-28751 about this.
> However we do have MariaDB 10.11.1 in Debian now. Maybe you Daniel can
> for the sake of it check if the behaviour is still same on 10.11?
Unfortunately, still the same.
I created a li
Hi!
I don't see anything new in upstream
https://jira.mariadb.org/browse/MDEV-28751 about this.
However we do have MariaDB 10.11.1 in Debian now. Maybe you Daniel can
for the sake of it check if the behaviour is still same on 10.11?
I would personally also be keen to figure out how to make the M
Control: forwarded -1 https://jira.mariadb.org/browse/MDEV-28751
Hi Daniel!
Thank you very much for your detailed report, your tests and to have
filled a jira issue!
I am now also subscribed to MDEV-28751 and will talk with Daniel Black
to see how we can debug this and maybe check if this is an i
tags + upstream
Faustin,
I found a much simpler way to demonstrate my problem with
a Debian Bullseye Live image and MariaDB generic Linux server:
* debian-live-11.3.0-amd64-standard.iso
* mariadb-10.6.8-linux-systemd-x86_64.tar.gz
I decided to file a new bug upstream:
[DEV-28751] mariadb
Faustin,
DL> I will give this a try. I'm curious what filesystem the container uses.
$ podman exec -it sys-test findmnt -J /
{
"filesystems": [
{
"target": "/",
"source": "fuse-overlayfs",
"fstype": "fuse.fuse-overlayfs",
"options":
"rw,nodev,noatime,
Faustin,
> I am not able to reproduce this with the latest
> mariadb-server-10.6-dbgsym version (10.6.8).
> Can you try with the latest version and tell me?
Yes, I tried 10.6.8-1 with the same result.
> Also, can you describe a bit better your setup? If this is a filesystem
> related issue, I
> > sudo rm -rf /var/lib/mysql/*
> > sudo -u mysql mariadb-install-db
Thanks Faustin, something was fixed between 10.6.7-3 and 10.6.8-1 that
made mariadb-install-db succeed for me since today morning.
With the March packages it kept failing every time during or after the
InnoDB initialization (as
Hi Denys,
I am not sure that the problem is the same, in your case it seems that
the datadir does not exist or need to be recreated.
If you are sure that nothing can be lost (or that you have backups), you
should try the following:
| sudo systemctl stop mariadb
| sudo rm -rf /var/lib/mysql/*
| sud
Hi Daniel!
Thanks for your detailed report.
I am not able to reproduce this with the latest
mariadb-server-10.6-dbgsym version (10.6.8).
Can you try with the latest version and tell me?
Also, can you describe a bit better your setup? If this is a filesystem
related issue, I would like to try to
Hello. The apt install of mariadb-server-10.6 fails for me too,
with the same line "Could not execute systemctl" but different
journal messages. I removed the existing setup in /etc and /var,
purged dependencies, but install still fails. How do I debug?
systemd[1]: Starting MariaDB 10.6.7 database
Package: mariadb-server-10.6
Version: 1:10.6.7-3
Severity: important
Debian MariaDB Maintainers,
Live Build (--distribution testing) image from April 2022.
8 GB RAM, so should be plenty of disk space available.
$ sudo apt install mariadb-server-10.6-dbgsym
...
Setting up mariadb-server-10.6 (1:1
17 matches
Mail list logo
