Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.0.16, 5.5(EOL), 10.0(EOL)
-
Windows 2008 R2 64Bit
Description
If we repair the table(s) and start the database, it works until someone tries to access a corrupt row. Then we can repair again but then again as someone tries to access a corrupt row it crashes again.
We tried to repair it using aria_chk with every possible method/option and afterwards trying to do a mysqldump but it just crashes after reaching some row.
The error we get from mysqldump:
G:\MariaDB\bin>mysqldump greyhound items_protocols -u root > items_protocols.txt
mysqldump: Error 1030: Got error 22 "Invalid argument" from storage engine Aria when dumping table `items_protocols` at row: 38910855
We even tried to delete those rows or exclude them using a where clause with the mysqldump command.
Here the create table statement:
CREATE TABLE `items_protocols` (
|
`i_id` bigint(20) NOT NULL AUTO_INCREMENT,
|
`i_item_r` int(11) NOT NULL DEFAULT '0',
|
`i_user_r` int(11) NOT NULL DEFAULT '0',
|
`c_rulename` varchar(64) NOT NULL DEFAULT '',
|
`c_text` varchar(32768) NOT NULL DEFAULT '',
|
`d_created` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
|
PRIMARY KEY (`i_id`),
|
KEY `i_item_r` (`i_item_r`)
|
) ENGINE=Aria AUTO_INCREMENT=1033130995 DEFAULT CHARSET=latin1 PAGE_CHECKSUM=1 TRANSACTIONAL=1
|
And our my.ini:
[mysqld]
|
character-set-server=latin1
|
datadir=G:/MariaDB/data/
|
enable-named-pipe
|
key_buffer_size=64K
|
aria_pagecache_buffer_size=8192M
|
max_allowed_packet=32M
|
max_connections=512
|
myisam_max_sort_file_size=100G
|
myisam_sort_buffer_size=64M
|
port=3306
|
query_cache_limit=8M
|
query_cache_size=32M
|
query_cache_type=1
|
read_buffer_size=512K
|
read_rnd_buffer_size=1M
|
sort_buffer_size=4M
|
sql-mode="NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"
|
thread_cache_size=128
|
tmp_table_size=8M
|
thread_handling=pool-of-threads
|
thread_pool_min_threads=64
|
thread_pool_max_threads=1024
|
Any suggestions what we could try other than we already did?
Attachments
Issue Links
- relates to
-
MDEV-26533 MariaDB 10.5 and 10.6 crashes with key_buffer_size greater than 4Gb on Windows 64bit
- Closed