Your message dated Sat, 6 Oct 2018 17:51:24 +0200
with message-id
<CAGVGHmvfrp=H29Qd-CVTEzah=zdhgdxwhhkxm4d6vfq9864...@mail.gmail.com>
and subject line Re: [debian-mysql] Bug#910454: mysql-server: Restoring backup
hangs for a large database
has caused the Debian Bug report #910454,
regarding mysql-server: Restoring backup hangs for a large database
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
910454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910454
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mysql-server
Version: 5.5.9999+default
Severity: normal
Dear Maintainer,
I am unable to restore a backup of a large database. Here I was
attempting to copy it by backing it up and restoring it.
What I did:
$ mysqldump --databases mythconverg > dump.myth
$ vi dump.myth
# Change the first few lines to change the name of the database from
# mythconverg to mythcopy and not fail if it already exists
$ mysql
MariaDB [(none)]> create database mythcopy;
MariaDB [(none)]> use mythcopy;
MariaDB [(none)]> source dump.myth;
...
Query OK, 21749 rows affected (0.22 sec)
Records: 21749 Duplicates: 0 Warnings: 0
...
Query OK, 21767 rows affected (0.20 sec)
Records: 21767 Duplicates: 0 Warnings: 0
There are lots of query records like the above, then it just stops, and
hangs for at least half an hour, probably forever.
I am able to use the mysql command line client on other databases, but not
on mythcopy. mysqld is not using any significant CPU or disk I/O according
to top and iotop. And /var/lib/mysql is on an SSD.
Googling shows a few bugs in the MySQL bug tracker, but nothing obvious
w.r.t. MariaDB, so there may be an upstream fix in MySQL but not
necessarily in MariaDB.
-- System Information:
Debian Release: 9.5
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-8-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
Versions of packages mysql-server depends on:
ii default-mysql-server 1.0.2
mysql-server recommends no packages.
mysql-server suggests no packages.
-- debconf-show failed
--- End Message ---
--- Begin Message ---
Sure
On Sat, Oct 6, 2018 at 5:23 PM, Matthew Toseland
<[email protected]> wrote:
> On 06/10/2018 16:15, Olaf van der Spek wrote:
>>
>> Hi Matthew,
>>
>> What does mytop or "show processlist" say?
>>
>>> mysqldump --databases mythconverg > dump.myth
>>
>>
>> mysqldump mythconverg is simpler, the name of the database won't be
>> included in the file so you can more easily restore it to a different
>> name.
>>
>> Gr,
>>
>> Olaf
>>
> My fault, disk full. Please close bug. :)
--
Olaf
--- End Message ---
