Bug #43555 | mysqlcheck exits 0 althought corruption found | ||
---|---|---|---|
Submitted: | 11 Mar 2009 9:42 | Modified: | 11 Mar 2009 15:45 |
Reporter: | Robert Heinzmann | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: MyISAM storage engine | Severity: | S3 (Non-critical) |
Version: | 4.0.27, 5.0.67, 5.0.80-bzr, 5.1 | OS: | Linux |
Assigned to: | CPU Architecture: | Any | |
Tags: | mysqlcheck |
[11 Mar 2009 9:42]
Robert Heinzmann
[11 Mar 2009 15:45]
Valeriy Kravchuk
Indeed, it returns exit code 0 for almost all cases (besides wrong options): valeriy-kravchuks-macbook-pro:5.0 openxs$ bin/mysqlcheck --check test tmi test.tmi Error : Can't find file: 'tmi' (errno: 2) error : Corrupt valeriy-kravchuks-macbook-pro:5.0 openxs$ echo $? 0 valeriy-kravchuks-macbook-pro:5.0 openxs$ bin/mysqlcheck --HECK test tmi bin/mysqlcheck: unknown option '--HECK' valeriy-kravchuks-macbook-pro:5.0 openxs$ echo $? 2