Here comes a rather dangerous error, I've googled for it but not found anything relevant.
Every time I reboot my system, the InnoDB data is being reset with the following message/error in /var/lib/mysql/error.log:
131015 15:54:34 [Note] Plugin 'FEDERATED' is disabled.
131015 15:54:34 InnoDB: The InnoDB memory heap is disabled
131015 15:54:34 InnoDB: Mutexes and rw_locks use GCC atomic builtins
131015 15:54:34 InnoDB: Compressed tables use zlib 1.2.7
131015 15:54:34 InnoDB: Using Linux native AIO
131015 15:54:34 InnoDB: Initializing buffer pool, size = 42.0M
131015 15:54:34 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file /media/Spiegel/mysql-datafiles/ibdata1 did not exist:
InnoDB: a new database to be created!
131015 15:54:34 InnoDB: Setting file /media/Spiegel/mysql-datafiles/ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
131015 15:54:34 InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 10 MB
InnoDB: Database physically writes the file full: wait...
131015 15:54:34 InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: 127 rollback segment(s) active.
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
131015 15:54:36 InnoDB: Waiting for the background threads to start
131015 15:54:37 InnoDB: 5.5.32 started; log sequence number 0
131015 15:54:37 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
131015 15:54:37 [Note] - '127.0.0.1' resolves to '127.0.0.1';
131015 15:54:37 [Note] Server socket created on IP: '127.0.0.1'.
131015 15:54:38 [Note] Event Scheduler: Loaded 0 events
131015 15:54:38 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.32-0ubuntu0.13.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
I have the following setup:
- OS 1: Regular Linux Mint 15 64-bit OS with regular mysql-server package installed, which means: mysqld Ver 5.5.32-0ubuntu0.13.04.1 for debian-linux-gnu on x86_64 ((Ubuntu)). Used to have Ubuntu 11.04 and MySQL 5.5 - worked fine then.
- OS 2: Windows XP, can dual boot into this.
- Data located on an NTFS drive using hardlink in fstab, here's the lines there:
/dev/mapper/nvidia_cebagebb1 /media/Spiegel ntfs nls=iso8859-1,users,umask=000,user,nobootwait 0 0
/media/Spiegel/mysql-datafiles/ /var/lib/mysql none bind,rw,exec 0 0
(/dev/mapper/nvidia_cebagebb1 is nvidia RAID, 2 disks, Mint sets up this itself - works as a regular drive, formatted as NTFS, mounted at /media/Spiegel)
- My /etc/mysql/my.cnf looks like this (lines starting with # removed):
[client]
port = 3306
socket = /var/run/mysqld/mysqld.sock
[mysqld_safe]
socket = /var/run/mysqld/mysqld.sock
nice = 0
[mysqld]
user = root
socket = /var/run/mysqld/mysqld.sock
port = 3306
basedir = /usr
datadir = /media/Spiegel/mysql-datafiles
tmpdir = /tmp
skip-external-locking
bind-address = 127.0.0.1
key_buffer = 16M
max_allowed_packet = 16M
thread_stack = 192K
thread_cache_size = 8
myisam-recover = BACKUP
query_cache_limit = 1M
query_cache_size = 16M
log_error = /var/log/mysql/error.log
expire_logs_days = 10
max_binlog_size = 100M
default-storage-engine = innodb
innodb_data_home_dir=/media/Spiegel/mysql-datafiles
innodb_additional_mem_pool_size=2M
innodb_flush_log_at_trx_commit=1
innodb_log_buffer_size=1M
innodb_buffer_pool_size=42M
innodb_log_file_size=10M
innodb_thread_concurrency=8
[mysqldump]
quick
quote-names
max_allowed_packet = 16M
[mysql]
[isamchk]
key_buffer = 16M
!includedir /etc/mysql/conf.d/
- apparmor is not installed according to ps ax and synaptic.
The error does not occour if just restart the mysql service, doing sudo service mysql restart. Only when I reboot the whole system, like sudo reboot or pull out the plug.
Currently I've moved ALL my database tables away from InnoDB to MyISAM (dumped, replaced InnoDB with MyISAM in dump file, imported using source in client). MyISAM works.
When I had the database tables as InnoDB and this had happened I could list the tables.
But when I tried to access them (DESC tablename for example) all I got was an error about table not found.
I've tried to delete the databases (works) and started over with clean database and import, did not help. It keeps recreating the InnoDB datafiles every reboot.
The reason the data is located on an NTFS drive is that I've got a dual boot system and sometimes I want to access the databases using Windows XP. Worked fine when I had Ubuntu 11.04 instead of Linux Mint 15 (based on Ubuntu 13.04).
Someone may say "You-should-not-dual-boot-mysql-db" - OK, I'm fine with that for a start. But I have not booted Windows XP, I'm just rebooting Linux Mint 15 and my data is located on an NTFS drive. Every reboot my InnoDB is driven over like a wild animal on a highway.
This error is rather poisonous - I'm not feeling safe with InnoDB anymore.
Why is not my InnoDB data persistant in Linux when I have the data located on an NTFS drive?
Every time I reboot my system, the InnoDB data is being reset with the following message/error in /var/lib/mysql/error.log:
131015 15:54:34 [Note] Plugin 'FEDERATED' is disabled.
131015 15:54:34 InnoDB: The InnoDB memory heap is disabled
131015 15:54:34 InnoDB: Mutexes and rw_locks use GCC atomic builtins
131015 15:54:34 InnoDB: Compressed tables use zlib 1.2.7
131015 15:54:34 InnoDB: Using Linux native AIO
131015 15:54:34 InnoDB: Initializing buffer pool, size = 42.0M
131015 15:54:34 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file /media/Spiegel/mysql-datafiles/ibdata1 did not exist:
InnoDB: a new database to be created!
131015 15:54:34 InnoDB: Setting file /media/Spiegel/mysql-datafiles/ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
131015 15:54:34 InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 10 MB
InnoDB: Database physically writes the file full: wait...
131015 15:54:34 InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: 127 rollback segment(s) active.
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
131015 15:54:36 InnoDB: Waiting for the background threads to start
131015 15:54:37 InnoDB: 5.5.32 started; log sequence number 0
131015 15:54:37 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
131015 15:54:37 [Note] - '127.0.0.1' resolves to '127.0.0.1';
131015 15:54:37 [Note] Server socket created on IP: '127.0.0.1'.
131015 15:54:38 [Note] Event Scheduler: Loaded 0 events
131015 15:54:38 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.32-0ubuntu0.13.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
I have the following setup:
- OS 1: Regular Linux Mint 15 64-bit OS with regular mysql-server package installed, which means: mysqld Ver 5.5.32-0ubuntu0.13.04.1 for debian-linux-gnu on x86_64 ((Ubuntu)). Used to have Ubuntu 11.04 and MySQL 5.5 - worked fine then.
- OS 2: Windows XP, can dual boot into this.
- Data located on an NTFS drive using hardlink in fstab, here's the lines there:
/dev/mapper/nvidia_cebagebb1 /media/Spiegel ntfs nls=iso8859-1,users,umask=000,user,nobootwait 0 0
/media/Spiegel/mysql-datafiles/ /var/lib/mysql none bind,rw,exec 0 0
(/dev/mapper/nvidia_cebagebb1 is nvidia RAID, 2 disks, Mint sets up this itself - works as a regular drive, formatted as NTFS, mounted at /media/Spiegel)
- My /etc/mysql/my.cnf looks like this (lines starting with # removed):
[client]
port = 3306
socket = /var/run/mysqld/mysqld.sock
[mysqld_safe]
socket = /var/run/mysqld/mysqld.sock
nice = 0
[mysqld]
user = root
socket = /var/run/mysqld/mysqld.sock
port = 3306
basedir = /usr
datadir = /media/Spiegel/mysql-datafiles
tmpdir = /tmp
skip-external-locking
bind-address = 127.0.0.1
key_buffer = 16M
max_allowed_packet = 16M
thread_stack = 192K
thread_cache_size = 8
myisam-recover = BACKUP
query_cache_limit = 1M
query_cache_size = 16M
log_error = /var/log/mysql/error.log
expire_logs_days = 10
max_binlog_size = 100M
default-storage-engine = innodb
innodb_data_home_dir=/media/Spiegel/mysql-datafiles
innodb_additional_mem_pool_size=2M
innodb_flush_log_at_trx_commit=1
innodb_log_buffer_size=1M
innodb_buffer_pool_size=42M
innodb_log_file_size=10M
innodb_thread_concurrency=8
[mysqldump]
quick
quote-names
max_allowed_packet = 16M
[mysql]
[isamchk]
key_buffer = 16M
!includedir /etc/mysql/conf.d/
- apparmor is not installed according to ps ax and synaptic.
The error does not occour if just restart the mysql service, doing sudo service mysql restart. Only when I reboot the whole system, like sudo reboot or pull out the plug.
Currently I've moved ALL my database tables away from InnoDB to MyISAM (dumped, replaced InnoDB with MyISAM in dump file, imported using source in client). MyISAM works.
When I had the database tables as InnoDB and this had happened I could list the tables.
But when I tried to access them (DESC tablename for example) all I got was an error about table not found.
I've tried to delete the databases (works) and started over with clean database and import, did not help. It keeps recreating the InnoDB datafiles every reboot.
The reason the data is located on an NTFS drive is that I've got a dual boot system and sometimes I want to access the databases using Windows XP. Worked fine when I had Ubuntu 11.04 instead of Linux Mint 15 (based on Ubuntu 13.04).
Someone may say "You-should-not-dual-boot-mysql-db" - OK, I'm fine with that for a start. But I have not booted Windows XP, I'm just rebooting Linux Mint 15 and my data is located on an NTFS drive. Every reboot my InnoDB is driven over like a wild animal on a highway.
This error is rather poisonous - I'm not feeling safe with InnoDB anymore.
Why is not my InnoDB data persistant in Linux when I have the data located on an NTFS drive?