RE: ERROR 33 - AIO WRITE ERROR

"Smith, Christopher L." <[email protected]>
Newsgroups gmane.comp.db.mysql.bugs,gmane.comp.db.mysql.windows
Message-ID <3080E1264732244B844860A7BD823A69015D8855@NAHOU-MSMBX07V.corp.enron.com>
Sinisa -
 
The error repeats itself whenever I attempt to restart mysqld/mysqld-nt/etc with the usual or debut settings.  Is there a particular way that I can capture the data for you such that it would be useful?  
 
Also, I will tell you that I moved the directory over to a new server, and mysql/innodb appeared able to load the file (i.e., make it past this error).  That might indicate a problem on the host related to disk read/write or something (hardware or software/who knows).
 
Chris

	-----Original Message----- 
	From: Sinisa Milivojevic [mailto:[email protected]] 
	Sent: Sat 12/20/2003 2:24 PM 
	To: Smith, Christopher L. 
	Cc: [email protected]; [email protected] 
	Subject: Re: ERROR 33 - AIO WRITE ERROR
	
	

	Smith, Christopher L. writes: 
	> All - 
	> 
	> This error hit me last night and I'm not quite sure what to make of it. I've researched the documentation and only found one reference to Error 33 within the INNODB & MYSQL documentation, but this wasn't helpful. I don't know if it is a bug or not, but I cannot make a test script because I cannot restart mysql under any state.  Would much appreciate any ideas.

	> 
	> Here is what I recovered from the 'err' file - the trace is attached below: 
	> 
	> MySql: ready for connections. 
	> Version: '4.0.16-nt'  socket: ''  port: 3306 
	> 031220  9:00:47  InnoDB: Operating system error number 33 in a file operation. 

	Hi! 

	The above truly looks like our bug. 

	It is either our bug or some memory corruption, because if you get 
	'Numerical argument out of domain' in the write operation, that is 
	truly a heavy error. 

	However, I do not see how can we repeat that. 

	I have looked at the trace and it seems that it has been started after 
	that error was raised. 

	We would be happy if you would come up with fully repeatable test 
	case, that would always lead to this error. 

	Thanks in advance. 

	-- 

	Sincerely, 

	-- 
	For technical support contracts, go to https://order.mysql.com/?ref=msmi 
	   __  ___     ___ ____  __ 
	  /  |/  /_ __/ __/ __ \/ /    Mr. Sinisa Milivojevic <[email protected]> 
	 / /|_/ / // /\ \/ /_/ / /__   MySQL AB 
	/_/  /_/\_, /___/\___\_\___/   Fulltime Developer and Support Coordinator 
	       <___/   www.mysql.com   Larnaca, Cyprus 



**********************************************************************
This e-mail is the property of Enron Corp. and/or its relevant affiliate and may contain confidential and privileged material for the sole use of the intended recipient (s). Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender or reply to Enron Corp. at [email protected] and delete all copies of the message. This e-mail (and any attachments hereto) are not intended to be an offer (or an acceptance) and do not create or evidence a binding and enforceable contract between Enron Corp. (or any of its affiliates) and the intended recipient or any other party, and may not be relied on by anyone as the basis of a contract by estoppel or otherwise. Thank you. 
**********************************************************************
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.