Different resource size - failed copy

[adrianlambert]

I'm consistently getting copy errors when backing up from my laptop to a samba share.

The backed up files seem fine but my script won't move the files from the laptop because they failed verification.

Anyone know how to avoid it?

 

This appears typical of the error.

 

 

>

*File "index/Users/Shared/Shoots/TEST20100511/Northerly20100505RAW/Northerly20100505_8440.CR2": different resource size (src: 1091, dest: 0)

necoIncoming: cmd 300 [ 612 bytes]: 63 70 53 46 00 00 00 00 00 00 00 04 01 01 00 00

necoIncoming: cmd 300 [ 4 bytes]: 72 44 74 53

necoIncoming: cmd 300 [ 612 bytes]: 64 45 64 52 00 00 00 00 00 00 00 04 01 01 00 00

necoIncoming: cmd 300 [ 4 bytes]: 6e 44 64 52

necoIncoming: cmd 300 [ 4 bytes]: 72 44 74 53

necoIncoming: cmd 300 [1276 bytes]: 67 42 64 52 00 00 00 00 00 00 00 05 00 01 00 00

[Mayoff]

I believe necoIncoming is just debug logging that you can ignore. What other types of errors are you getting?

 

The file above changed size during the copy process. Maybe a problem related to the destination.

[CallMeDave]

I'm consistently getting copy errors when backing up from my laptop to a samba share.

 

Are you Backing Up, or are you Copying?

Is this to a Media Set with the CIFS share as a Member? Or are you using a Copy Script "from the laptop" to the network volume?

 

different [color:purple]resource size[/color] (src: 1091, dest: 0)

 

Your CIFS volume doesn't support Mac resource forks, so it's getting lost in the copy operation.

Depending on the file, the resource fork might contain only an old-school custom icon or the like.

Doing actual backups will avoid this issue, as the files are enclosed within Retrospect's Member format.

 

 

Dave

[adrianlambert]

I can't backup at this stage to a set as it's just field data from a laptop that will be used on the network, then gets backed up from a server.

 

Is it possible to have a rule set up to ignore resource forks? Do they appear as any sort of file that can be filtered?