11/05/2007, 2:35pm, EST
Monday, November 5th
Leopard: Data loss, AirPort issues
There is reportedly a major bug in Leopard's directory-moving code, which manifests in the Finder, that can lead to significant data loss if a destination volume (where a file is being moved) disappears while a move operation is in action. The bug is reported and described on Tom Karpik's blog, and involves a situation where a file is copied from one volume to another. A test setup by Karpik involves an SMB server and a MacBook Pro running VMWare. Essentially, the directory to be copied will be deleted if the destination is closed down in the middle of the process.
Meanwhile, Apple has documented an issue in Leopard where after installing the Login and Keychain Update 1.0, the computer's AirPort card may not work. Apple says the solution is to start up in Safe Mode by holding the Shift key during startup. Once the computer has started in Safe Mode, simply restart again (without holding any keys).
On a related note, some manufacturers of wireless adapters for Macs are updating their software and drivers for Leopard compatibility. QuickerTek has updated its complete line of Quicky and nQuicky wireless signal boosters for Mac OS 10.5 These new QuickerTek drivers avoid the problems reported by early users of Leopard and wireless networking.
Filed under: Apple
,
, 10
,
,
,
,
,

subscribe to comments
for this article
http://discussions.apple.com/thread.jspa?threadID=1195706&tstart=15
DO NOT BUY the AEBS until Apple fix this!
So you're saying the problem isn't Apple's, it's people who are stupid enough to use an option that exists in the OS? And it's more than two steps. And it may require you to perform actions you don't want to perform (for example, if you have a 10 GB file on drive A, you want to move to drive B, you'd have to copy it, verify the copy is there (you don't want to delete the original until you're sure, right?), then delete the original. But you need to empty the trash to save the disk space, which you may not want to do (and you need to wait until that's done before you can then perform the action you wanted to save the 10GB for in the first place).
Do you always copy files, even within folders on the same drive? Or do you change your behavior because you know where you're moving it?
And, of course, it all requires you to know that you're planning on moving between disks or not between disks.
And why wouldn't you use it if its available?
Is move a new feature? As far as I knew, the Mac NEVER allowed move between volumes. Was this feature added in Leopard?
No, this is NOT a new feature. Move between volumes has been available in Tiger, at least. Just drag a file and hold the command key while dropping. It moves (yet, oddly enough, apparently doesn't cause the original to delete prematurely).
Shame on them if it was. I think you should NEVER delete a source if between two volumes - leave that up to the users discretion.
It is up to the user's discretion. That's why you have the option. But it shows Apple's programmers work more on shortcuts to get the UI to work responsively, vs. data integrity.
Makes you wonder how many other issues might be floating through.