linux tarball binaries segfault on failed aio setup

Bug #793390 reported by Stewart Smith
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL Server
Unknown
Unknown
Percona Server moved to https://jira.percona.com/projects/PS
Status tracked in 5.7
5.1
Invalid
Undecided
Unassigned
5.5
Fix Released
Low
Unassigned
5.6
Invalid
Undecided
Unassigned
5.7
Invalid
Undecided
Unassigned

Bug Description

110606 17:03:41 InnoDB: Warning: io_setup() failed with EAGAIN. Will make 5 attempts before giving up.
InnoDB: Warning: io_setup() attempt 1 failed.
InnoDB: Warning: io_setup() attempt 2 failed.
InnoDB: Warning: io_setup() attempt 3 failed.
InnoDB: Warning: io_setup() attempt 4 failed.
InnoDB: Warning: io_setup() attempt 5 failed.
110606 17:03:43 InnoDB: Error: io_setup() failed with EAGAIN after 5 attempts.
InnoDB: You can disable Linux Native AIO by setting innodb_native_aio = off in my.cnf
Segmentation fault (core dumped)

Revision history for this message
Stewart Smith (stewart) wrote :
Changed in percona-server:
status: New → Confirmed
importance: Undecided → Critical
milestone: none → 5.5.13-20.4
Revision history for this message
Stewart Smith (stewart) wrote :

from io_setup man page:

       EAGAIN The specified nr_events exceeds the user's limit of available
              events.

so we're probably hitting that.

Changed in percona-server:
status: Confirmed → Triaged
Revision history for this message
Stewart Smith (stewart) wrote :

probably upstream too

<gval> stewart: yep, about bug - http://forums.mysql.com/read.php?11,406737,406737

Revision history for this message
Stewart Smith (stewart) wrote :

sysctl fs.aio-max-nr is set to 65536 by default on Ubuntu. As a test, I set this to 1,000,000 and things seemed to go better. We should have a better fallback in this situation.

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

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

seems detected as bug of InnoDB-5.5

And anyway, at the situation, InnoDB cannot start.
Abort seems not so bad behavior.

Revision history for this message
Stewart Smith (stewart) wrote :

Seeing as it is upstream, and there is workarounds... I'm changing to LOW for us.

Changed in percona-server:
importance: Critical → Low
milestone: 5.5.13-20.4 → none
tags: added: innodb upstream
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-2643

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.