MySQL shutting down because of Operating system error 1784

--001636e0b9650f88a704799aae7b
Content-Type: text/plain; charset=ISO-8859-1

Hi,

We are getting "InnoDB: Operating system error number 1784" error on MySQL
and it just shuts down after getting the error.

This happens once every 2 days or so. We are using MySQL
5.0.51b-community-nt.

I was wondering if anyone had this problem before?

Here's the full error output:
InnoDB: Operating system error number 1784 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-erro r-codes.html
InnoDB: File name D:\MySQLlog\ib_logfile0
InnoDB: File operation call: 'Windows aio'.
InnoDB: Cannot continue operation.
InnoDB: Log scan progressed past the checkpoint lsn 35 1443981126

Is it because of not being able to write log files for some reason? Is
InnoDB logs required?

Thanks!
Cagdas

--001636e0b9650f88a704799aae7b--

RE: MySQL shutting down because of Operating system error 1784

If you have a lot of InnoDB transactions, maybe your ib_logfile0 and ib_log=
file1 are too small.

Transactional data are written in these files in a circular fashion. You ma=
y have run out of space in these.

If you want to make these files bigger, simply do the following:

1) Use the setting "innodb_log_file_size=3D" in my.ini
2) net stop mysql
3) del D:\MySQLlog\ib_logfile*
4) net start mysql (during startup of mysqld, ib_logfile0 and ib_logfile1 a=
re recreated)

As a rule of thumb, set innodb_log_file_size =3D (25% of innodb_buffer_pool=
_size)
BTW the combined total of all ib_logfiles cannot exceed 4GB.

Example: if innodb_buffer_pool_size=3D1G, then set innodb_log_file_size=3D2=
56M
Example: if innodb_buffer_pool_size=3D512M, then set innodb_log_file_size=
=3D128M
Example: if innodb_buffer_pool_size=3D256M, then set innodb_log_file_size=
=3D64M
Etc...

Rolando A. Edwards
MySQL DBA (SCMDBA)

155 Avenue of the Americas, Fifth Floor
New York, NY 10013
212-625-5307 (Work)
201-660-3221 (Cell)
AIM & Skype : RolandoLogicWorx
redwards@logicworks.net
http://www.linkedin.com/in/rolandoedwards

-----Original Message-----
From: Cagdas CUBUKCU [mailto:cagdascubukcu@gmail.com]=20
Sent: Monday, November 30, 2009 1:19 PM
To: mysql@lists.mysql.com
Subject: MySQL shutting down because of Operating system error 1784

Hi,

We are getting "InnoDB: Operating system error number 1784" error on MySQL
and it just shuts down after getting the error.

This happens once every 2 days or so. We are using MySQL
5.0.51b-community-nt.

I was wondering if anyone had this problem before?

Here's the full error output:
InnoDB: Operating system error number 1784 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-erro r-codes.html
InnoDB: File name D:\MySQLlog\ib_logfile0
InnoDB: File operation call: 'Windows aio'.
InnoDB: Cannot continue operation.
InnoDB: Log scan progressed past the checkpoint lsn 35 1443981126

Is it because of not being able to write log files for some reason? Is
InnoDB logs required?

Thanks!
Cagdas

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=3Dgcdmg-mysql-2@m.gmane.o rg

Re: MySQL shutting down because of Operating system error 1784

Cagdas CUBUKCU gmail.com> writes:

>
> Hi,
>
> We are getting "InnoDB: Operating system error number 1784" error on MySQL
> and it just shuts down after getting the error.



# ERROR_INVALID_USER_BUFFER or ERROR_NOT_ENOUGH_MEMORY Each device
driver maintains a fixed-size list (in a nonpaged pool) of
outstanding I/O requests. If this list is full, the system can’t
queue your request, ReadFile and WriteFile return FALSE, and
GetLast-Error reports one of these two error codes (depending on the
driver).

Apart from increasing your log file size, can you check the number of
i/o processes and if some other process is doing i/o as well. I think
windows has some processonitor for this.



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org

Re: MySQL shutting down because of Operating system error 1784

--00504502b535c11694047a07656d
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi all,

Thanks for your suggestions. The problem is solved I guess, no problems
reported after I made the changes.

As suggested, increased the log file sizes.

Changed innodb_buffer_pool_size from 128M to 256M.
Changed innodb_log_file_size from 5M to 64M.

Also changed innodb_thread_concurrency from 20 to 8. This might have helped
as well.

-Cagdas

On Mon, Nov 30, 2009 at 3:57 PM, Raj Shekhar wrote=
:

> Cagdas CUBUKCU gmail.com> writes:
>
> >
> > Hi,
> >
> > We are getting "InnoDB: Operating system error number 1784" error on
> MySQL
> > and it just shuts down after getting the error.
>
>
>
> # ERROR_INVALID_USER_BUFFER or ERROR_NOT_ENOUGH_MEMORY Each device
> driver maintains a fixed-size list (in a nonpaged pool) of
> outstanding I/O requests. If this list is full, the system can=92t
> queue your request, ReadFile and WriteFile return FALSE, and
> GetLast-Error reports one of these two error codes (depending on the
> driver).
>
> Apart from increasing your log file size, can you check the number of
> i/o processes and if some other process is doing i/o as well. I think
> windows has some processonitor for this.
>
>
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:
> http://lists.mysql.com/mysql?unsub=3Dcagdascubukcu@gmail.com
>
>

--00504502b535c11694047a07656d--

Re: MySQL shutting down because of Operating system error 1784

--001636e0a80c1ad263047b03357c
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Ok, it's been some time since this problem, but we could finally resolve it=
..
I wanted to report back here so it gets archived and helps anyone who has a
similar problem in the future.

Since the server is a virtual server, there is a Sync Driver that quiescies
the hard drive before VMWare takes a snapshot. This process stops all I/O
requests to the drive and makes MySQL crash with the error code mentioned
below.

So, it looks like disabling the Sync Driver did the trick.

Thanks,
Cagdas

On Sat, Dec 5, 2009 at 8:01 PM, Cagdas CUBUKCU wro=
te:

> Hi all,
>
> Thanks for your suggestions. The problem is solved I guess, no problems
> reported after I made the changes.
>
> As suggested, increased the log file sizes.
>
> Changed innodb_buffer_pool_size from 128M to 256M.
> Changed innodb_log_file_size from 5M to 64M.
>
> Also changed innodb_thread_concurrency from 20 to 8. This might have help=
ed
> as well.
>
> -Cagdas
>
>
> On Mon, Nov 30, 2009 at 3:57 PM, Raj Shekhar wrot=
e:
>
>> Cagdas CUBUKCU gmail.com> writes:
>>
>> >
>> > Hi,
>> >
>> > We are getting "InnoDB: Operating system error number 1784" error on
>> MySQL
>> > and it just shuts down after getting the error.
>>
>>
>>
>> # ERROR_INVALID_USER_BUFFER or ERROR_NOT_ENOUGH_MEMORY Each device
>> driver maintains a fixed-size list (in a nonpaged pool) of
>> outstanding I/O requests. If this list is full, the system can=92t
>> queue your request, ReadFile and WriteFile return FALSE, and
>> GetLast-Error reports one of these two error codes (depending on the
>> driver).
>>
>> Apart from increasing your log file size, can you check the number of
>> i/o processes and if some other process is doing i/o as well. I think
>> windows has some processonitor for this.
>>
>>
>>
>> --
>> MySQL General Mailing List
>> For list archives: http://lists.mysql.com/mysql
>> To unsubscribe:
>> http://lists.mysql.com/mysql?unsub=3Dcagdascubukcu@gmail.com
>>
>>
>

--001636e0a80c1ad263047b03357c--