Bug #21303 file system corrupted when opening a dump file in Win XP
Submitted: 26 Jul 2006 20:22 Modified: 27 Aug 2006 6:24
Reporter: Dana Benciu Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Administrator Severity:S1 (Critical)
Version:not sure OS:Windows (Windows XP)
Assigned to: Assigned Account CPU Architecture:Any
Tags: corrupted files, file system, linux, windows xp

[26 Jul 2006 20:22] Dana Benciu
Description:
I tried to open a dump file created on a Linux machine, under a text editor (WordPad) in Windows XP. After that I started to get corrupted files errors on the Windows machine partition where the dump file resided and ultimately Windows XP would not reboot without performing a file system check, with lots of files being affected (indexes, etc.). The whole database has at least one table with a BLOB field and a size of less than 40 MB in total.

How to repeat:
Open a dump file created on a Linux machine, under Windows XP. I think it's a good idea for testing purposes to have BLOB fields in some of the tables.

Suggested fix:
To indicate alternate programs that can be used to safely open a dump file on a different platform than the one it was created on (especially when trying to open it under Windows XP, I don't remember to have encountered such issues on Linux), since that file doesn't necessarily need to be open with restore purposes, but just to retrieve a portion of it in the form of a text content (for example few KB of text).
[27 Jul 2006 6:24] Sveta Smirnova
Thank you for the report.

But why you choose "MySQL Administrator" category for it? Did you create dump using MySQL Administrator or mysqldump?

Also note, WordPad is not plain text editor. We can not guarantee what any program working on Windows can open dumps without problem. So, please try to open the dump using Notepad and say us result.
[27 Aug 2006 23:00] Bugs System
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".