MySQL Bugs: #43097: mysqldump doesn't export all my records. Missing a lot of rows

Bug #43097	mysqldump doesn't export all my records. Missing a lot of rows
Submitted:	23 Feb 2009 6:34	Modified:	6 May 2009 16:25
Reporter:	Jonas Nyberg	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: mysqldump Command-line Client	Severity:	S2 (Serious)
Version:	mysqldump Ver 10.11 Distrib 5.0.67, for	OS:	Windows (Windows 2003 Std)
Assigned to:		CPU Architecture:	Any
Tags:	mysqldump failing to dump records Incoherently. Backup is inconsistent and missi

Description:
I use Mysqldump to export all my tables row to a datafile. The table contains around 100 rows every day with 12 columns where 1 column is blob.

After the export, I remove all the entries from the table.
mysqldump -u root --password=****** --skip-add-drop-table --no-create-db --no-create-info db imgtable > export_data.sql

The problem is that only a few entries are exported and it's missing a lot of rows. I'm wondering why this is happening and can't figure out why it doesn't just dump the whole table...

Any help would be much appreciated. 

How to repeat:
- Install MySQL 5.0.67 for win2k3 std.
- Create a database and create table: 
- CREATE TABLE `tbl_staging_approved` (`app_id` int(11) unsigned NOT NULL,`image_name` varchar(250) NOT NULL,`image` longblob NOT NULL,`ic` char(12) NOT NULL,`name` varchar(100) NOT NULL,`email` varchar(100) NOT NULL,`house_pno` varchar(12) NOT NULL,`office_pno` varchar(12) NOT NULL,`hp` varchar(12) NOT NULL,`card_type` varchar(20) NOT NULL,`existing_cardno` char(16) default NULL,`app_date` date default NULL,`app_time` time default NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;SET character_set_client = @saved_cs_client;

- File the table with around 70 records and try and run the mysqldump command as described above.

Changed category because mysqldump belongs to command line client. BACKUP category is for SQL BACKUP from MySQL 6.0

Thank you for the report.

Please provide output of SHOW VARIABLES LIKE 'max_allowed_packet'

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