Assertion failure @ buf/buf0buf.c line 3241

Bug #423049 reported by trickie
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona-XtraDB
New
Undecided
Unassigned

Bug Description

This crash is occurring fairly regularly on several systems. It sometimes takes several days after a restore to occur again, but has occurred quite quickly after a restore.

We are using MySQL 5.1.34 + percona-xtradb-1.0.3-5 plugin. I am in the process of preparing an update to the latest 5.1.3x and the latest xtradb plugin, but will be running the above versions for some time yet.

Attached are the my.cnf and error log. If any further build/system options/info are needed let me know.

Revision history for this message
trickie (trickie) wrote :
Revision history for this message
trickie (trickie) wrote :
Revision history for this message
Vadim Tkachenko (vadim-tk) wrote : Re: [Bug 423049] Re: Assertion failure @ buf/buf0buf.c line 3241

I suggest you try
MySQL 5.1.37 + percona-xtradb-1.0.3-7

We fixed bunch of bugs related to what you describe.

Thanks,
Vadim

--
Vadim Tkachenko, CTO
Percona Inc.
ICQ: 369-510-335, Skype: vadimtk153, Phone +1-888-401-3403

Percona Training Workshops - 14 & 16 September, Santa Clara & San Francisco
http://www.percona.com/training/

On Wed, Sep 2, 2009 at 1:36 AM, trickie<email address hidden> wrote:
>
> ** Attachment added: "mysqld config"
>   http://launchpadlibrarian.net/31219692/my.cnf
>
> --
> Assertion failure @ buf/buf0buf.c line 3241
> https://bugs.launchpad.net/bugs/423049
> You received this bug notification because you are a member of Percona
> developers, which is the registrant for Percona-XtraDB.
>
> Status in Percona XtraDB Storage Engine for MySQL: New
>
> Bug description:
> This crash is occurring fairly regularly on several systems. It sometimes takes several days after a restore to occur again, but has occurred quite quickly after a restore.
>
> We are using MySQL 5.1.34 + percona-xtradb-1.0.3-5 plugin. I am in the process of preparing an update to the latest 5.1.3x and the latest xtradb plugin, but will be running the above versions for some time yet.
>
> Attached are the my.cnf and error log. If any further build/system options/info are needed let me know.
>

Revision history for this message
Yasufumi Kinoshita (yasufumi-kinoshita) wrote :

Could you tell us also which type of CPU you use?
I think you may not use x86 or x86_64 CPU.

Thank you.

Revision history for this message
trickie (trickie) wrote :
Download full text (3.6 KiB)

Hi, thanks for the response, I am aiming to test out those versions ASAP.

We use a x86_64 cpu, mainly quad cores, but also some others:

~ # cat /proc/cpuinfo

processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Xeon(R) CPU E5430 @ 2.66GHz
stepping : 6
cpu MHz : 2660.110
cache size : 6144 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 lahf_lm tpr_shadow vnmi flexpriority
bogomips : 5320.22
clflush size : 64
cache_alignment : 64
address sizes : 38 bits physical, 48 bits virtual
power management:

processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Xeon(R) CPU E5430 @ 2.66GHz
stepping : 6
cpu MHz : 2660.110
cache size : 6144 KB
physical id : 0
siblings : 4
core id : 2
cpu cores : 4
apicid : 2initial apicid : 2
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 lahf_lm tpr_shadow vnmi flexpriority
bogomips : 5320.03
clflush size : 64
cache_alignment : 64
address sizes : 38 bits physical, 48 bits virtual
power management:

processor : 2
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Xeon(R) CPU E5430 @ 2.66GHz
stepping : 6
cpu MHz : 2660.110
cache size : 6144 KB
physical id : 0
siblings : 4
core id : 1
cpu cores : 4
apicid : 1initial apicid : 1
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 lahf_lm tpr_shadow vnmi flexpriority
bogomips : 5320.05
clflush size : 64
cache_alignment : 64
address sizes : 38 bits physical, 48 bits virtual
power management:

processor : 3
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Xeon(R) CPU E5430 @ 2.66GHz
stepping : 6
cpu MHz : 2660.110
cache size : 6144 KB
physical id : 0
siblings : 4
core id : 3
cpu cores : 4
apicid : 3
initial apicid : 3
fpu : yes
fpu_exception : yes
cpuid...

Read more...

Revision history for this message
Yasufumi Kinoshita (yasufumi-kinoshita) wrote :

Sorry, it is duplicate of the bug405714.
And it is already fixed at the latest version.

Thank you.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.