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 reproduce it myself. I have tested with a systemd container that I have created for these kind of testing, here are the commands (using podman): | podman run --name sys-test --rm -d fauust/docker-systemd:debian-sid | podman exec -it sys-test bash -c "echo \"deb http://deb.debian.org/debian-debug/ sid-debug main\" >> /etc/apt/sources.list && apt update && apt install -y mariadb-server-10.6-dbgsym" Cheers! Daniel Lewart <lewa...@gmail.com>, 11/04/2022 – 00:20:00 (-0500): > 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:10.6.7-3) ... > Created symlink /etc/systemd/system/multi-user.target.wants/mariadb.service → > /lib/systemd/system/mariadb.service. > Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142. > ... > > $ sudo journalctl | grep -i mariadb | cut -c58- > [See below] > > Perhaps this is similar to: > #983002 - plocate: does not work with /var on overlayfs > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983002 > > Please let me know any additional information that you could use. > > Thank you! > Daniel Lewart > Urbana, Illinois > --- > 2022-04-10 22:53:02 0 [Warning] InnoDB: Retry attempts for writing partial > data failed. > 2022-04-10 22:53:02 0 [ERROR] InnoDB: Write to file ./ibdata1 failed at > offset 0, 1048576 bytes should have been written, only 0 were written. > Operating system error number 22. Check that your OS and file system support > files of this size. Check also that the disk is not full or a disk quota > exceeded. > 2022-04-10 22:53:02 0 [ERROR] InnoDB: Error number 22 means 'Invalid argument' > 2022-04-10 22:53:02 0 [ERROR] InnoDB: Could not set the file size of > './ibdata1'. Probably out of disk space > 2022-04-10 22:53:02 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. > 2022-04-10 22:53:02 0 [ERROR] InnoDB: Operating system error number 22 in a > file operation. > 2022-04-10 22:53:02 0 [ERROR] InnoDB: Error number 22 means 'Invalid argument' > 2022-04-10 22:53:02 0 [ERROR] InnoDB: File (unknown): 'close' returned OS > error 222. Cannot continue operation > 220410 22:53:02 [ERROR] mysqld got signal 6 ; > This could be because you hit a bug. It is also possible that this binary > or one of the libraries it was linked against is corrupt, improperly built, > or misconfigured. This error can also be caused by malfunctioning hardware. > > To report this bug, see https://mariadb.com/kb/en/reporting-bugs > > We will try our best to scrape up some info that will hopefully help > diagnose the problem, but since we have already crashed, > something is definitely wrong and this may fail. > > Server version: 10.6.7-MariaDB-3 > key_buffer_size=134217728 > read_buffer_size=131072 > max_used_connections=0 > max_threads=153 > thread_count=0 > It is possible that mysqld could use up to > key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467957 > K bytes of memory > Hope that's ok; if not, decrease some variables in the equation. > > Thread pointer: 0x0 > Attempting backtrace. You can use the following information to find out > where mysqld died. If you see no messages after this, something went > terribly wrong... > stack_bottom = 0x0 thread_stack 0x49000 > 2022-04-10 22:53:02 0 [ERROR] InnoDB: Operating system error number 9 in a > file operation. > 2022-04-10 22:53:02 0 [ERROR] InnoDB: Error number 9 means 'Bad file > descriptor' > 2022-04-10 22:53:02 0 [ERROR] InnoDB: File (unknown): 'close' returned OS > error 209. Cannot continue operation > Printing to addr2line failed > /usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x555d0aa77f0e] > /usr/sbin/mariadbd(handle_fatal_signal+0x478)[0x555d0a5c5268] > 2022-04-10 22:53:02 0 [ERROR] InnoDB: Operating system error number 9 in a > file operation. > 2022-04-10 22:53:02 0 [ERROR] InnoDB: Error number 9 means 'Bad file > descriptor' > 2022-04-10 22:53:02 0 [ERROR] InnoDB: File (unknown): 'close' returned OS > error 209. Cannot continue operation > /lib/x86_64-linux-gnu/libpthread.so.0(+0x12200)[0x7f606ba96200] > 2022-04-10 22:53:02 0 [ERROR] InnoDB: Operating system error number 9 in a > file operation. > 2022-04-10 22:53:02 0 [ERROR] InnoDB: Error number 9 means 'Bad file > descriptor' > 2022-04-10 22:53:02 0 [ERROR] InnoDB: File (unknown): 'close' returned OS > error 209. Cannot continue operation > /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x141)[0x7f606b57a8a1] > /lib/x86_64-linux-gnu/libc.so.6(abort+0x112)[0x7f606b564546] > 2022-04-10 22:53:02 0 [ERROR] InnoDB: Operating system error number 9 in a > file operation. > 2022-04-10 22:53:02 0 [ERROR] InnoDB: Error number 9 means 'Bad file > descriptor' > 2022-04-10 22:53:02 0 [ERROR] InnoDB: File (unknown): 'close' returned OS > error 209. Cannot continue operation > /usr/sbin/mariadbd(+0x63b8e9)[0x555d0a2638e9] > /usr/sbin/mariadbd(+0xcb66e5)[0x555d0a8de6e5] > /usr/sbin/mariadbd(+0xdbc308)[0x555d0a9e4308] > /usr/sbin/mariadbd(+0xdbc371)[0x555d0a9e4371] > /usr/sbin/mariadbd(+0xdbea20)[0x555d0a9e6a20] > /usr/sbin/mariadbd(+0xdbfb41)[0x555d0a9e7b41] > /usr/sbin/mariadbd(+0xd2585f)[0x555d0a94d85f] > /usr/sbin/mariadbd(+0xc64245)[0x555d0a88c245] > /usr/sbin/mariadbd(_Z24ha_initialize_handlertonP13st_plugin_int+0x7e)[0x555d0a5c839e] > /usr/sbin/mariadbd(+0x797a76)[0x555d0a3bfa76] > /usr/sbin/mariadbd(_Z11plugin_initPiPPci+0x828)[0x555d0a3c0a38] > /usr/sbin/mariadbd(+0x6c367a)[0x555d0a2eb67a] > /usr/sbin/mariadbd(_Z11mysqld_mainiPPc+0x404)[0x555d0a2f1224] > 2022-04-10 22:53:02 0 [ERROR] InnoDB: Operating system error number 9 in a > file operation. > 2022-04-10 22:53:02 0 [ERROR] InnoDB: Error number 9 means 'Bad file > descriptor' > 2022-04-10 22:53:02 0 [ERROR] InnoDB: File (unknown): 'close' returned OS > error 209. Cannot continue operation > /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xcd)[0x7f606b5657fd] > 2022-04-10 22:53:02 0 [ERROR] InnoDB: Operating system error number 9 in a > file operation. > 2022-04-10 22:53:02 0 [ERROR] InnoDB: Error number 9 means 'Bad file > descriptor' > 2022-04-10 22:53:02 0 [ERROR] InnoDB: File (unknown): 'close' returned OS > error 209. Cannot continue operation > /usr/sbin/mariadbd(_start+0x2a)[0x555d0a2e680a] > The manual page at > https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ > contains > information that should help you find out what is causing the crash. > Writing a core file... > Working directory at /var/lib/mysql > Resource Limits: > Limit Soft Limit Hard Limit Units > Max cpu time unlimited unlimited seconds > Max file size unlimited unlimited bytes > Max data size unlimited unlimited bytes > Max stack size 8388608 unlimited bytes > Max core file size 0 0 bytes > Max resident set unlimited unlimited bytes > Max processes 29195 29195 processes > Max open files 32190 32190 files > Max locked memory 976257024 976257024 bytes > Max address space unlimited unlimited bytes > Max file locks unlimited unlimited locks > Max pending signals 29195 29195 signals > Max msgqueue size 819200 819200 bytes > Max nice priority 0 0 > Max realtime priority 0 0 > Max realtime timeout unlimited unlimited us > Core pattern: core > > /usr/bin/mysql_install_db: line 541: 7508 Aborted > "$mysqld_bootstrap" $defaults $defaults_group_suffix "$mysqld_opt" > --bootstrap $silent_startup "--basedir=$basedir" "--datadir=$ldata" > --log-warnings=0 --enforce-storage-engine="" "--plugin-dir=${plugindir}" > $args --max_allowed_packet=8M --net_buffer_length=16K > > Installation of system tables failed! Examine the logs in > /var/lib/mysql for more information. > > The problem could be conflicting information in an external > my.cnf files. You can ignore these by doing: > > shell> /usr/bin/mysql_install_db --defaults-file=~/.my.cnf > > You can also try to start the mysqld daemon with: > > shell> /usr/sbin/mariadbd --skip-grant-tables --general-log & > > and use the command line tool /usr/bin/mariadb > to connect to the mysql database and look at the grant tables: > > shell> /usr/bin/mysql -u root mysql > mysql> show tables; > > Try 'mysqld --help' if you have problems with paths. Using > --general-log gives you a log in /var/lib/mysql that may be helpful. > > The latest information about mysql_install_db is available at > https://mariadb.com/kb/en/installing-system-tables-mysql_install_db > You can find the latest source at https://downloads.mariadb.org and > the maria-discuss email list at https://launchpad.net/~maria-discuss > > Please check all of the above before submitting a bug report > at https://mariadb.org/jira > > ### > _______________________________________________ > pkg-mysql-maint mailing list > pkg-mysql-ma...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-mysql-maint -- Faustin
signature.asc
Description: PGP signature
