Notice different behavior for Win7 "copy" vs "move" - data recovery

[surfyogi]

I am recovering a drive I pulled out of a hot swap box ( the drive lost the drivepool partition because I didn't unmount the drive from Windows first). 

 

I now have all the recovered folders/files sitting on a spare drive (thanks to WonderShare Data Recovery) and am slowing copying them back to the pool.

 

My questions is this: 

Is there some difference between using Windows 7 copy, vs Win7 move? (as far as the drivepool emulation is concerned?)

 

What I have noticed is this:  (I know how to force Windows to copy or move, as I need to of course)

 

a) If I use "copy", I may or may not get a "merge folders" dialog, and a "these files are already present, replace or no?) dialogs. If I use copy,

it will often times just look like its copying, I will come back after some time, expecting to see a merge dialog up, and I see nothing. No copy going on, no dialogs, nothing. Like it just copied the first few folders and then stopped?

 

If I use "move" on the other hand, it seems to always do a reliable deep transfer of files all the way down the tree, across all folders, very reliably. 

 

I was not aware to expect different behaviors between these 2 operations, except of course, files that are moved will be deleted from the source drive.

 

I am of course, copying from a spare recovered filed drive, to the emulated pooled drive.

I assume this is not a bug in windows. I'm thinking it's a bug in DrivePool filesystem emulation?

 

I'm on version: 2.1.1.561

 

Anyone else ever notice this behavior?

[Christopher (Drashna)]

For the drive in question, sometimes a CHKDSK pass on the drive will fix the issue. But that's not a guarantee. 

 

 

From a quick test, it does appear that copy and move operations are handled the same.

 

however, if you're doing this on the same disk, then it may be using "smart move" which does handle things different from a normal operation.