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 <cagdascubu...@gmail.com>wrote: > 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 <rajl...@rajshekhar.net>wrote: > >> Cagdas CUBUKCU <cagdascubukcu <at> 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. >> >> <http://msdn.microsoft.com/en-us/library/cc500408.aspx> >> >> # 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=cagdascubu...@gmail.com >> >> >
