Marc,
Sorry to see you encountered this.
I searched https://jira.mariadb.org and cannot find a similar issue.
Can you please create a bug report.
A mariadbackup might hit exactly the same issue. A mysqldump/restore
will regenerate the innodb space listed as corrupt.
On Fri, Nov 5, 2021 at 3:45
Ah. Great question Gordon.
RAM: 8x Samsung 16GB DDR4 2R (ECC)
Processor: 2x 2.1GHz Intel Xeon-Broadwell (E5-2620-V4)
Motherboard: SuperMicro X10DRU-i+_R1.02b
Drive Controller: LSI Avago MegaRAID 9361-8i
Drives: 4x Intel S3710
On 2021-11-04 2:56 p.m., Gordan Bobic wrote:
What hardware are yo
What hardware are you on, and does it have ECC memory?
On Thu, Nov 4, 2021 at 7:48 PM Michael Caplan wrote:
>
> Hello,
>
> I have a nothing fancy SQL statement that crashes MariaDB 10.3.31. The
> error log reports "mysqld got signal 11" with the below included mini
> core dump.
>
> The statement
Hello,
I have a nothing fancy SQL statement that crashes MariaDB 10.3.31. The
error log reports "mysqld got signal 11" with the below included mini
core dump.
The statement caused no issues with my prior install of 10.2.xx. With
10.3, the statement runs the majority of the time. The vast m
Hello - I have ran into a problem that maybe someone else has hit and
knows a solution for it. I recently upgraded my OpenSuSE 15.2 x64
version to OpenSuSE 15.3 x64 and installed all additional updates and
patches that were suggested for 15.3. Most of the upgrade succeeded, all
except Mariad
5 matches
Mail list logo
