ports/134148: InnoDB fails after upgrading MySQL from 5.0.51 to 5.077 on FreeBSD 6.2

Mark Stosberg mark at summersault.com
Fri May 1 22:20:01 UTC 2009


>Number:         134148
>Category:       ports
>Synopsis:       InnoDB fails after upgrading MySQL from 5.0.51 to 5.077 on FreeBSD 6.2
>Confidential:   no
>Severity:       critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri May 01 22:20:00 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Mark Stosberg
>Release:        FreeBSD 6.2-RELEASE
>Organization:
Summersault, LLC
>Environment:
FreeBSD vhost1.summersault.com 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Apr 27 15:36:05 EDT 2007     root at foo.summersault.com:/usr/src/sys/i386/compile/FOO  i386

>Description:
There is a bug when upgrading MySQL from 5.0.55 to MySQL 5.0.77 on FreeBSD, such that InnoDB no longer works.  The error when starting is:

InnoDB: Unable to lock ./ibdata1, error: 22

Several others have experienced this issue and reported it to the MySQL project here:

http://bugs.mysql.com/bug.php?id=40621

But so far, the upstream project has not taken interest in a resolution.
>How-To-Repeat:
Upgrade the mysql50 port the usual way on FreeBSD 6.2
>Fix:
Manually downgrading works around the issue. 

>Release-Note:
>Audit-Trail:
>Unformatted:



More information about the freebsd-ports-bugs mailing list