A critical bug has been discovered in Leopard’s Finder, “directory moving code” module.
The problem is such that when a Mac user is moving folders from one storing device to another and for any reason the destination storing device disappears, then source data directory structure gets inconsistent. In normal case when we move a folder from one drive to another the source is deleted or modified when the consistency of both source and destination is matched. However, in the Leopard case the source is modified without checking the consistency of data.
It doesn’t make any difference either you are using any of these storing devices USB, SMB, FireWire etc you will experience the same discrepancy every where. So be careful when you are moving data from one device to another. You may in turn lose your critical data.
Till apple comes with an update and to avoid any data loss you should take precaution by copying the folder in same drive and then move the first copy to other location and then check the data consistency through folder size & directory structure. For those who have already lost their important files while moving folders from one device to another or any other reason then try Macintosh data recovery software.
Stellar Information has experience of more than 13 years in the field of data recovery software & services.
November 16th, 2007 at 1:51 pm
Is this the same trans-volume move bug that was fixed in the 10.5.1 update released on Thursday, Nov 15 2007 or is this a different issue?
The trans-volume move bug was fairly obscure since the Finder normally copies files between volumes and it doesn’t impact at all the moving of files on the same volume (which is common).
As I understand, the trans-volume move bug occurred when a user who wanted to have the original files deleted from the first volume as soon as the copy was done held down the command key when dragging files between volumes. If nothing interrupted the first step (copying the file to the new volume), all was fine and the files disappeared from the original volume as intended. It was just when something interrupted the copy step, the Finder considered it “done” and deleted the original rather than considering it an error and aborting the process altogether.
Is this a different bug?
November 19th, 2007 at 11:57 pm
The Mac OS X 10.5.1 Update updates Mac OS X Leopard version 10.5 to version 10.5.1
Apple has rectified the problem of data loss caused by moving files…
the Updates are as follows
System and Finder
* Addresses a potential data loss issue when moving files across partitions in the Finder.
* Resolves an issue with login after turning off FileVault for a specific user account.
* Improves compatibility with Adobe Flash-based uploaders used by .Mac Web Gallery and certain other websites and applications.
* Resolves a potential text drawing issue with certain Adobe Flash-based websites and applications.
Get the Apple updates from here
http://docs.info.apple.com/article.html?artnum=61798
February 10th, 2010 at 7:40 am
Hiya, great day! Your article is quite striking. I never believed that it was probable to do something like that until after I looked over your content. You definitely offered an incredible understanding on exactly how this kind of whole scheme operates. I will always return for more information. Keep writing!
March 6th, 2010 at 7:45 pm
I’m so glad to have found your web page. My pal mentioned it to me before, yet never got around to checking it out until now. I must express, I’m floored. I really enjoyed reading through your posts and will absolutely be back to get more.