MySQL Bugs: #36761: Error "Table is marked as crashed and should be repaired" on new CSV table

Bug #36761	Error "Table is marked as crashed and should be repaired" on new CSV table
Submitted:	16 May 2008 16:19	Modified:	27 Feb 2014 17:25
Reporter:	Cees Hesp	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server: CSV	Severity:	S1 (Critical)
Version:	5.1.24	OS:	Windows (XP)
Assigned to:		CPU Architecture:	Any

Description:
Hello,

I'm following the instructions in "Inside MySQL 5.1, A DBA's Perspective" to create an "empty" table using the CSV engine, and then replacing the .CSV file via the file system. Creating the table works fine, but when I try to query the newly created table (e.g. SELECT * FROM ..., or SELECT COUNT(*) FROM ...) an error is reported:

(error 1194): Table ... is marked as crashed and should be repaired.

It does not help to stop the MySQL service after creating the table

How to repeat:
See description

Thank you for a problem report. What exact version of MySQL server, 5.1.x, do you use?

Server version: 5.1.24-rc-community MySQL Community Server (GPL)

Please, send SHOW CREATE TABLE results for the CSV table you had created.

As you are on Windows, looks like your problem (and a solution) is described in user comment to http://dev.mysql.com/doc/refman/5.1/en/csv-storage-engine.html. Please, check. That whitepaper use example form Unix environment...

Changing the .CSV file to Unix format with PFE works. But this is a workaround, not a solution! I'm trying to automate loading the database... (and don't want manual intervention)

Problem with \r\n is not repeatable neither on Linux, nor on Mac.

Thank you for the feedback.

But in order to fix this bug we need to repeat it. Please provide repeatable test case, including all steps you do: how you connect to MySQL server, CREATE TABLE statement, what you do next.

Six years later, and now you are asking for a repeatable test case? Tssss.....
===================================
[21 Feb 19:23] Sveta Smirnova

Thank you for the feedback.

But in order to fix this bug we need to repeat it. Please provide repeatable test case, including all steps you do: how you connect to MySQL server, CREATE TABLE statement, what you do next.
===================================

could this really be a duplicate of mine?
http://bugs.mysql.com/bug.php?id=71299

Thank you for the feedback.

Bug was analyzed by a person who left the company, this is why it occurred on my radar. Anyway, 6 years before I tried to repeat it and was not able, so closing as "Can't repeat". If you will be able to provide repeatable test case feel free to reopen the report. Check if this is not the same issue as bug #71299 first.