MySQL Bugs: #60014: MEB gives continous errors without proceeding to next step

Bug #60014	MEB gives continous errors without proceeding to next step
Submitted:	8 Feb 2011 18:28	Modified:	28 Feb 2011 22:27
Reporter:	Hema Sridharan	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Backup	Severity:	S3 (Non-critical)
Version:	MEB 3.6	OS:	Linux
Assigned to:	Thava Alagu	CPU Architecture:	Any

Description:
MEB when notices a directory inside database directory it gets confused. It 
produces continuous errors that can be stopped only by hitting CTRL +C 

"mysqlbackup: Error reading file '/export/home2/tmp/mysql-5.1-meb-testing/mysql
-test/var/mysqld.1/data/mebdir/meta.dir' (Errcode: 21)"

How to repeat:
Repeat the same steps as mentioned in BUG#60013 (How to repeat section)  and it produces an error message that repeats the same again and again instead of advancing to the next directory.

For me (on Mac OS X), this is not different from bug #60013. Backup just stops on the database with directory inside. No continuous errors:

macbook-pro:meb-3.6 openxs$ bin/mysqlbackup -uroot --backup-dir=/tmp/backup backup

InnoDB Backup Utility v3.6.0 [2011/02/10] 
Copyright (c) 2003, 2011, Oracle and/or its affiliates. All Rights Reserved.

INFO: Starting with following command line ...
 bin/mysqlbackup -uroot --backup-dir=/tmp/backup backup 

INFO: Got some server configuration information from running server.

Created backup directory '/tmp/backup'
IMPORTANT: Please check that mysqlbackup run completes successfully.
            At the end of a successful 'backup' run mysqlbackup
            prints "mysqlbackup completed OK!".

--------------------------------------------------------------------
                       Server Repository Options:
--------------------------------------------------------------------
  datadir                          =  /Users/openxs/dbs/5.5/data/
  innodb_data_home_dir             =  
  innodb_data_file_path            =  ibdata1:10M:autoextend
  innodb_log_group_home_dir        =  /Users/openxs/dbs/5.5/data/
  innodb_log_files_in_group        =  2
  innodb_log_file_size             =  5242880

--------------------------------------------------------------------
                       Backup Config Options:
--------------------------------------------------------------------
  datadir                          =  /tmp/backup
  innodb_data_home_dir             =  /tmp/backup
  innodb_data_file_path            =  ibdata1:10M:autoextend
  innodb_log_group_home_dir        =  /tmp/backup
  innodb_log_files_in_group        =  2
  innodb_log_file_size             =  5242880

 mysqlbackup: INFO: Unique generated backup id for this is 12973651094985000 
 mysqlbackup: INFO: System tablespace file format is Antelope.
 mysqlbackup: INFO: Found checkpoint at lsn 1743176.
 mysqlbackup: INFO: Starting log scan from lsn 1742848.
110210 21:11:49 mysqlbackup: INFO: Copying log...
110210 21:11:49 mysqlbackup: INFO: Log copied, lsn 1743176.
          We wait 1 second before starting copying the data files...
110210 21:11:50 mysqlbackup: INFO: Copying /Users/openxs/dbs/5.5/data/ibdata1 (Antelope file format).
 mysqlbackup: INFO: Preparing to lock tables: Connected to mysqld server.
110210 21:11:51 mysqlbackup: INFO: Starting to lock all the tables....
110210 21:11:51 mysqlbackup: INFO: All tables are locked and flushed to disk
 mysqlbackup: INFO: Opening backup source directory '/Users/openxs/dbs/5.5/data/'
110210 21:11:51 mysqlbackup: INFO: Starting to backup all files in subdirectories of '/Users/openxs/dbs/5.5/data/'
 mysqlbackup: INFO: Backing up the database directory 'mysql'
 mysqlbackup: INFO: Backing up the database directory 'performance_schema'
 mysqlbackup: INFO: Backing up the database directory 's1'
mysqlbackup: Error reading file '/Users/openxs/dbs/5.5/data/s1/deleteme' (Errcode: 21)
 mysqlbackup: ERROR: Cannot backup table `s1`.`deleteme`
 mysqlbackup: ERROR: Cannot backup database 's1'
 mysqlbackup: ERROR: Backup of non-innodb tables failed.!
110210 21:11:51 mysqlbackup: INFO: All tables unlocked
Error: operation failed.
macbook-pro:meb-3.6 openxs$ 

Do I miss something?

You have not verified exactly what I mentioned in BUG#60013. You need to do the following,

1. Run mysqlbackup where backup dir is sub dir of data dir. Note that this fails as destination dir cannot be sub dir of source dir
2. Now again run backup where backup-dir is some other location (say
--backup-dir=export/home2/tmp/bkpdir)
3. Verify that 2nd run of backup also results in error as 
Error reading file
'/export/home2/tmp/mysql-5.1-meb-testing/mysql-
test/var/mysqld.1/data/mebdir/meta.dir' (Errcode: 21)

Notice that BUG#60013 describes about MEB getting confused by seeing a directory (and so gives msg as "Error reading file"). The OS error code (21) is about "Missing file".

Whereas this is not the case for BUG#60014. It mentions that error message does not stop until CTRL +C button is  hit. It is expected that error msg should be issued only once and advance to next directory. This does not happen in reality.
So there are 2 issues here
a. Continuous errors  (BUG#60014)
b. MEB getting confused by directories inside datadir and looks for only files.(BUG#60013)

I was not able to reproduce continuous error message problem. As far as the subdirectory issue, the database directory is expected to have only files, no subdirectory, the latest patch gives more clear error message to that effect. Just let me know if you are able to reproduce continuous error msg problem with the latest patch, if not, please close the bug.

This issue is not reproducible anymore. I am closing the bug report. Thanks for fixing the issue. The error message is more intuitive now.