8 messages in com.mysql.lists.bugsRE: ERROR 33 - AIO WRITE ERROR
FromSent OnAttachments
Smith, Christopher L.20 Dec 2003 11:41 
Sinisa Milivojevic20 Dec 2003 12:24 
Smith, Christopher L.20 Dec 2003 13:51 
Heikki Tuuri21 Dec 2003 08:14 
Smith, Christopher L.21 Dec 2003 11:09 
Sinisa Milivojevic22 Dec 2003 04:04 
Heikki Tuuri22 Dec 2003 06:09 
Smith, Christopher L.22 Dec 2003 07:29 
Subject:RE: ERROR 33 - AIO WRITE ERROR
From:Smith, Christopher L. (Chri@ENRON.com)
Date:12/20/2003 01:51:04 PM
List:com.mysql.lists.bugs

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:sin@mysql.com] Sent: Sat 12/20/2003 2:24 PM To: Smith, Christopher L. Cc: bu@lists.mysql.com; win@lists.mysql.com 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 <sin@mysql.com> / /|_/ / // /\ \/ /_/ / /__ 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
enro@enron.com 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. **********************************************************************