MySQL Bugs: #21782: mysqldump does not dump db with more than 330 tables under win32 with option -l

Bug #21782	mysqldump does not dump db with more than 330 tables under win32 with option -l
Submitted:	22 Aug 2006 13:17	Modified:	22 Sep 2006 16:36
Reporter:	nicolas tricart	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	5.0.24	OS:	Windows (Windows)
Assigned to:		CPU Architecture:	Any
Tags:	--lock-tables, bug #17089, error file .frm does not exist, mysqldump

Description:
when dumping a database with more than 330 tables on windows with --lock-tables option, mysqldump output is :
mysqldump: Got error: 1017: Can't find file: '.\sica\docblob_649.frm' (errno: 24) when using LOCK TABLES

The error message is not correct: the file does exist and the table is ok. If I drop the table docblob_649, I have the same message on the next table (docblob_650). If I drop the table docblob_648, I have the same error on table docblob_651, passing docblob_650.
That's why I'm sure it's a problem of number of tables ...

Looks like bug #17089

How to repeat:
create a database with more than 330 tables
do a mysqldump --lock-tables

Thank you for the bug report. I created 400 tables in the test database
and starting the server with the defaults options and then I got what
you reported:

c:\mysql\bin>mysqld-nt --standalone --console
060822 13:22:10  InnoDB: Started; log sequence number 0 52493
060822 13:22:10 [Note] mysqld-nt: ready for connections.
Version: '5.0.24-community-nt'  socket: ''  port: 3306  MySQL Community Edition (GPL)
060822 13:24:03 [ERROR] mysqld-nt: Can't open file: '.\test\tb324.frm' (errno: 24)
060822 13:24:03 [ERROR] mysqld-nt: Can't open file: '.\test\tb324.frm' (errno: 24)

Then I started the server with:

c:\mysql\bin>mysqld-nt --standalone --console --open-files-limit=2048
060822 13:26:41  InnoDB: Started; log sequence number 0 52493
060822 13:26:41 [Note] mysqld-nt: ready for connections.
Version: '5.0.24-community-nt'  socket: ''  port: 3306  MySQL Community Edition (GPL)

see above: --open-files-limit=2048 which is the maximum currently of
file descriptors that Windows server support and tested again without
any problems. Please try the same.

Thanks in advance.

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".

Same issue on MySQL 4.1.20-max-log
with a database with 7609 tables

mysqldump --quote-names --add-drop-table --all --quick --lock-tables --disable-keys --force database

database$ find -name \*\.MYI | wc -l
7609

database$ find | wc -l
22829