InnoDB: Check also that the disk is not full or a disk quota exceeded.
InnoDB: Error number 49 means 'Disc quota exceeded'.
InnoDB: Some operating system error numbers are described at
InnoDB:
http://dev.mysql.com/doc/refman/5.0/en/operating-system-error-codes.html
100508 20:31:08InnoDB: Assertion failure in thread 3 in file os0file.c line 4026
InnoDB: Failing assertion: ret
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to
http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB:
http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
100508 20:31:08 - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.
key_buffer_size=0
read_buffer_size=1048576
max_used_connections=0
max_connections=210
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 645120 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
100508 20:31:08 mysqld restarted
100508 20:31:08 [Warning] Can't create test file /bdd/sqlprive-lm44527-001.lower-test
100508 20:31:08 [Warning] Can't create test file /bdd/sqlprive-lm44527-001.lower-test
InnoDB: Log scan progressed past the checkpoint lsn 46 3035375463
100508 20:31:08 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 46 3040617984
InnoDB: Doing recovery: scanned up to log sequence number 46 3043833424
100508 20:31:09 InnoDB: Error: Write to file /bdd/ib_logfile0 failed at offset 0 1536.
InnoDB: 512 bytes should have been written, only -1 were written.
InnoDB: Operating system error number 49.
InnoDB: Check that your OS and file system support files of this size.
InnoDB: Check also that the disk is not full or a disk quota exceeded.
InnoDB: Error number 49 means 'Disc quota exceeded'.
InnoDB: Some operating system error numbers are described at
InnoDB:
http://dev.mysql.com/doc/refman/5.0/en/operating-system-error-codes.html
100508 20:31:09InnoDB: Assertion failure in thread 3 in file os0file.c line 4026
InnoDB: Failing assertion: ret
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to
http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB:
http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
100508 20:31:09 - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.
key_buffer_size=0
read_buffer_size=1048576
max_used_connections=0
max_connections=210
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 645120 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
100508 20:31:09 mysqld restarted
100508 20:31:09 [Warning] Can't create test file /bdd/sqlprive-lm44527-001.lower-test
100508 20:31:09 [Warning] Can't create test file /bdd/sqlprive-lm44527-001.lower-test
Fatal error: Can't remove the pid file: /bdd/sqlprive-lm44527-001.pid at Sat May 8 20:31:17 CEST 2010
Fatal error: Can't remove the pid file: /bdd/sqlprive-lm44527-001.pid at Sat May 8 20:39:20 CEST