(Conflict) and trouble syncing to Amazon Cloud

I recently had to re-mount my NAS drive and afterwards help ODrive find the “missing” folders. When the folders were re-synced they were re-sent to Amazon. I’m not sure why ODrive didn’t notice these were already in Amazon (de-dup). Also, when ODrive was syncing my pictures it changed any picture with a psd extension and added (conflict) to the filename. Now Lightroom cannot find any picture that has (conflict) in the filename and I will have to “find” each file. Finally, ODrive is also syncing the same pictures continuously.

Hi,
It sounds like you are setup to backup your NAS to Amazon. Is this correct?

Were the folders you needed to re-map “sync to odrive” folders?

odrive should’ve avoided re-upload with the data already in the cloud, so I am not sure why that occurred.

If you can send me a diagnostic from the odrive tray menu, I can take a look at the current unexpected behavior. I will need the details of the unexpected behavior you are seeing along with some specific file paths.

Thanks!

I sent the diagnostics. My other issues cleared up but odrive is still re-syncing all files when I reboot the laptop. When I click on Stop Sync the Waiting goes up to over 8000 files.

This is a strange one. It seems that on mounting the dates of the files on the NAS are read as being 1 day earlier than they were before. Exactly 1 day (86400 seconds).

I would like to focus on a single file so that we can try to track its reported time between mounts of the external volume. This file should suffice for that test:
/Volumes/Public/Software/WD Software/WD SmartWare/dotnetfx35.exe

Let’s try the following:
Open a terminal session and run:
stat -s /Volumes/Public/Software/WD Software/WD SmartWare/dotnetfx35.exe

Record the output.

Now restart your system, and when it comes up again run the same command:
stat -s /Volumes/Public/Software/WD Software/WD SmartWare/dotnetfx35.exe

Can you post the results here along with sending another diagnostic after the second step?

Thanks!

Report sent. Here are the outputs from the terminal session:

Last login: Fri Aug 12 21:28:20 on ttys000
Hectors-MBP:~ HMG$ stat -s /Volumes/Public/Software/WD Software/WD SmartWare/dotnetfx35.exe
stat: /Volumes/Public/Software/WD: stat: No such file or directory
stat: Software/WD: stat: No such file or directory
stat: SmartWare/dotnetfx35.exe: stat: No such file or directory
Hectors-MBP:~ HMG$

Last login: Fri Aug 12 21:30:30 on console
Hectors-MBP:~ HMG$ stat -s /Volumes/Public/Software/WD Software/WD SmartWare/dotnetfx35.exe
stat: /Volumes/Public/Software/WD: stat: No such file or directory
stat: Software/WD: stat: No such file or directory
stat: SmartWare/dotnetfx35.exe: stat: No such file or directory
Hectors-MBP:~ HMG$

Whoops. I forgot the quotes around the path:
stat -s "/Volumes/Public/Software/WD Software/WD SmartWare/dotnetfx35.exe"

Sorry about that…

Resent diagnostics

Last login: Fri Aug 12 21:33:34 on ttys000
Hectors-MBP:~ HMG$ stat -s "/Volumes/Public/Software/WD Software/WD SmartWare/dotnetfx35.exe"
st_dev=771751941 st_ino=67615 st_mode=0100777 st_nlink=1 st_uid=501 st_gid=20 st_rdev=0 st_size=242743296 st_atime=1298325332 st_mtime=1298325332 st_ctime=1298325332 st_birthtime=1298325332 st_blksize=65536 st_blocks=474112 st_flags=0
Hectors-MBP:~ HMG$

Last login: Fri Aug 12 21:40:02 on console
Hectors-MBP:~ HMG$ stat -s "/Volumes/Public/Software/WD Software/WD SmartWare/dotnetfx35.exe"
st_dev=771751940 st_ino=67615 st_mode=0100777 st_nlink=1 st_uid=501 st_gid=20 st_rdev=0 st_size=242743296 st_atime=1298325332 st_mtime=1298325332 st_ctime=1298325332 st_birthtime=1298325332 st_blksize=65536 st_blocks=474112 st_flags=0
Hectors-MBP:~ HMG$

Hi @hgarcell,
It is hard to tell what is happening here, but the times reported by the OS keep changing. If we take this file as an example (/Volumes/Public/Software/WD Software/WD SmartWare/dotnetfx35.exe), this is what we’ve seen for the modified time so far, in order (according to the diagnostics):

1st instance: 1298325332 - Tue, 22 Feb 2011 17:25:32 GMT
2nd instance: 1298309132 - Mon, 21 Feb 2011 17:25:32 GMT
3rd instance: 1298395532 - Mon, 21 Feb 2011 21:55:32 GMT

The 3rd instance, which is from the most recent diagnostic matches your own command from the terminal, so we know the times are being recorded correctly. I can’t account for why the times keep changing though.

I’m still looking, but I wanted to give you a heads up.

If you run the same command again, are you still seeing the “1298395532” time, or has it changed again?

Last login: Fri Aug 12 21:41:45 on ttys000
Hectors-MBP:~ HMG$ stat -s "/Volumes/Public/Software/WD Software/WD SmartWare/dotnetfx35.exe"
st_dev=771751942 st_ino=67615 st_mode=0100777 st_nlink=1 st_uid=501 st_gid=20 st_rdev=0 st_size=242743296 st_atime=1298309132 st_mtime=1298309132 st_ctime=1298309132 st_birthtime=1298309132 st_blksize=65536 st_blocks=474112 st_flags=0
Hectors-MBP:~ HMG$

It looks like the time changed again… I am a little stumped here. If the time keeps being reported as different we are going to keep trying to sync it, thinking that something has changed.

Can you tell me what NAS this is?

Western Digital - My Book Live 2TB

Any updates on this. I haven’t used ODrive as it keeps seeing all files as new.

Hi @hgarcell,
Unfortunately I was never able to reproduce this issue myself. Since the system keeps telling us that the dates have changed, odrive will continue to think it needs to re-upload the files.

Is this external drive used by any other computers or applications?

Yes. Since it is a NAS Drive there are at least two computers accessing the drive. One PC / One MAC. Only the MAC has ODrive installed and syncing the NAS to AWS.

Have you syncing the NAS on the PC to see if it experiences the same issue?

Also, do you know what procotol is used to connect the drive on OSX? You can look at this by running the mount command from the terminal. Maybe using a different protocol would help (afp vs cifs vs smb).

I am running AFP. I will try the different protocols. If that doesn’t work I will try from the PC.

1 Like

Thanks for taking the time to experiment. I am curious to see what the result is.