MySQL Bugs: #54214: "could not backup existing file" "result too large"

Bug #54214	"could not backup existing file" "result too large"
Submitted:	3 Jun 2010 17:52	Modified:	17 Jun 2010 14:58
Reporter:	Abu Abdillah	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	5.2.22	OS:	Windows (XP Pro SP3 FR)
Assigned to:		CPU Architecture:	Any
Tags:	saving file error mysql workbench

Description:
My wmb file is exactly : 123Kb (126 821 bytes) which takes on disk :124Kb (126 976 bytes)

and I cannot add any new element or change any existing element since all changes would be lost when trying to save them on disk.

The exact message box contains the following informations:

TITLE: Could not save document to <Path and Filename>

ICON: Error (red circle with white cross)

CONTENT: Could not backup existing file
         <Path and Filename>: Result
         too large

BUTTON: Close

How to repeat:
try to haev a big file worth 124Kb and try editing it.

You'll have that message.

Suggested fix:
Allow to save the file even the backup couldn't be created.

Description:
My wmb file is exactly : 123Kb (126 821 bytes) which takes on disk :124Kb (126 976
bytes)

and I cannot add any new element or change any existing element since all changes would
be lost when trying to save them on disk.

The exact message box contains the following informations:

TITLE: Could not save document to <Path and Filename>

ICON: Error (red circle with white cross)

CONTENT: Could not backup existing file
         <Path and Filename>: Result
         too large

BUTTON: Close

How to repeat:
try to haev a big file worth 124Kb and try editing it.

You'll have that message.

Suggested fix:
Allow to save the file even the backup couldn't be created.

Thanks a lot for your time & efforts

Thank you for the bug report. Could you please provide the offended file project (private if you wish)?. Thanks in advance.

It looks like there is a workaround that I just found so I updated Severity.

It seems the problem may has nothing to do with the file size.

After have executed the forward engeneering, I've done a Reverse engeneering on the database created. the new filename's size is 54Kb instead of the 124Kb

I lost the inserts on my tables along with their colors in the EER but i can update my model now.

PS: I'll try to send the problematic file soon once I find a way to do it :)

I am not able to repeat this.

Are you sure that you won't have a hardware problem here?

Maybe your disk has a problem.

My HDD is OK... I don't know what's going on!

but the file is strangely too big in regards of the data in it.

Maybe check the content of the file with an external edit software to see if the data structure is OK.

If it's OK then just close the case, we'll blame Win XP's Hibernating process: since I'm using it a lot instead of shutting down the PC, and I've noticed that when using Hibernating too much, the OS behaves in an unexpected manner sometimes and I have to reboot it in order to have the software behave normally.

Thanks again for your time and efforts.

Thanks Abu. If you ever find more details about this or even a way to reproduce it reliable please come back and let us know.

Maybe I have the same issue by using "MySQL Workbench 5.2.25 CE" Rev 6303.

I build an ERR-Model and saved it to a file. After that I changed something and saved again. At least I deleted the *.bak File.

Now I try to load the file and I got the following in a MessageBox "cannot create directory for document" followed by a new MessageBox "result to large". After that MySQL Workbench is unable to do anything. By any Click either the Workbench does nothing or I got another MessageBox without any Text but the Head of the MessageBox shows "result to large".

It has nothing to do with WinXP hibernation because I did not hibernate but after restarting the workbench 2 times the files is successfully read.