Bug #28120 | Service cannot be started again after restart!! | ||
---|---|---|---|
Submitted: | 26 Apr 2007 13:06 | Modified: | 12 Mar 2008 14:03 |
Reporter: | Samoil Bugediwala | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server | Severity: | S1 (Critical) |
Version: | 5.0.45, 5.0.37 | OS: | Windows (XP Professional OEM) |
Assigned to: | CPU Architecture: | Any |
[26 Apr 2007 13:06]
Samoil Bugediwala
[27 Apr 2007 11:06]
Valeriy Kravchuk
Thank you for a problem report. Please, try to repeat with a newer version, 5.0.37. In case of the same problem, please, check if adding innodb_flush_method=unbuffered to my.ini makes any difference. Are you sure your RAID-1 working properly? (Read bug #8021 and bug #3139 for similar problems)
[30 Apr 2007 20:19]
Samoil Bugediwala
Thank you for the reply. I have already tested this MySQL v5.0.37 and I have also checked with alpha & beta versions. But still the problem is the same. I have doubled checked RAID1 & also have tried re-installing RAID but still the same problem remains with MySQL. Thank you, Samoil
[1 May 2007 9:23]
Valeriy Kravchuk
Thank you for a dditional checks. Have you checked with innodb_flush_method=unbuffered?
[1 Jun 2007 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[17 Jan 2008 22:31]
David Beechum
Same problem here, RAID 1 setup. I added innodb_flush_method=unbuffered to the default setup and it still will not restart the service. Using MySql 5.0.45 for Windows 32 bit I have an Adaptec Serial ATA Raid Card in the machine. ------ Error Log ---------------------------------------------------- 080117 15:56:07 InnoDB: Starting shutdown... 080117 15:56:09 InnoDB: Shutdown completed; log sequence number 0 43655 080117 15:56:09 [Note] C:\MySql\bin\mysqld-nt: Shutdown complete 080117 15:56:10 InnoDB: Operating system error number 87 in a file operation. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.0/en/operating-system-error-codes.html InnoDB: File name .\ib_logfile0 InnoDB: File operation call: 'aio read'. InnoDB: Cannot continue operation. 080117 15:56:39 InnoDB: Operating system error number 87 in a file operation. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.0/en/operating-system-error-codes.html InnoDB: File name .\ib_logfile0 InnoDB: File operation call: 'aio read'. InnoDB: Cannot continue operation. 080117 15:56:57 InnoDB: Operating system error number 87 in a file operation. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.0/en/operating-system-error-codes.html InnoDB: File name .\ib_logfile0 InnoDB: File operation call: 'aio read'. InnoDB: Cannot continue operation.
[30 Jan 2008 10:29]
Valeriy Kravchuk
I still think this is drivers-related problem. Please, upgrade XP and RAID drivers to latest versions available and inform about any results.
[1 Mar 2008 0:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[10 Mar 2008 21:59]
jahu ferdek
I have the same problem. I cannot start mysql as a service (the same problem: Operating system error number 87). It starts only first time after instaling mysql - then mysql creates files: ibdata1, ib_logfile0, ib_logfile1 and works perfectly. After restarting service it cannot run. Instead of that error, I can start mysql manualy by command line: mysqld-nt --defaults-file="C:\[...path...]\my.ini" Then it works witout any problem. My mysql version is 5.0.37, Windows XP SP2, my mainboard: Supermicro PDSME+, Xeon 3050, 2gb ram, RAID 1. After upgrading to 5.0.51a I cannot start mysql (even manualy), so I can use only 5.0.37.
[10 Mar 2008 22:59]
jahu ferdek
Right now I found, that there is the same problem that is in bug #28913. If I put line in my.ini: innodb_flush_method=normal mysql works perfectly.
[12 Mar 2008 14:03]
Susanne Ebrecht
I'll set this as duplicate of bug #28913 because there is a better description at this bug.
[23 Jun 2008 17:44]
Heikki Tuuri
The problem might be a file system block size that is > 16 kB. See the other bug report.