Hi, Ive recently upgraded to v3.18 and it seems to be a little different than
before. If i sync files and folders between drives on my pc, or across my
network pcs all is good, however if I sync a folder of around 40,000 files
from a folder on my d drive to my dlink nas box, it works, but if I go back to
compare after the sync is finished it tells me it has to update about 4,000
odd file attributes. If i tell it to proceed the progress bar goes instantly
to the end of sync, the transfer speed shows zero, and the number of files to
be updated scrolls from 4,000 odd to zero, when it tells me it was successful.
If i run compare after syncing any other drive or network pc this does not
happen
Help please
- Posts: 21
- Joined: 17 Jul 2011
-
- Site Admin
- Posts: 7211
- Joined: 9 Dec 2007
I assume the change in attributes is a different file modification date? This
looks to me like some buffering issue, where the dlink nas doesn't properly
set file times and unfortunately doesn't report any errors.
The second comparison detects this mismatch and adapts file modification date
only. This is naturally fast, and no (content) data needs to be transfered
(speed == 0). This second run seems to be successful finally.
FFS's approach when copying files is 1. copy file via Windows default API to
some temp file, 2. copy all file times, 3. rename temp file to actual file.
The correct file modification time is already set in 1, and redundantly set
again in 2. So FFS has done its best to have the dlink drive set the correct
value. All errors that are occuring are reported by FFS. I fear there is
nothing more to do from a software side to improve on.
looks to me like some buffering issue, where the dlink nas doesn't properly
set file times and unfortunately doesn't report any errors.
The second comparison detects this mismatch and adapts file modification date
only. This is naturally fast, and no (content) data needs to be transfered
(speed == 0). This second run seems to be successful finally.
FFS's approach when copying files is 1. copy file via Windows default API to
some temp file, 2. copy all file times, 3. rename temp file to actual file.
The correct file modification time is already set in 1, and redundantly set
again in 2. So FFS has done its best to have the dlink drive set the correct
value. All errors that are occuring are reported by FFS. I fear there is
nothing more to do from a software side to improve on.
- Posts: 21
- Joined: 17 Jul 2011
Thanks for the response, let me see if I can be more specific.
I have a folder on my D drive of my win 7 32bit home p pc that contains about
13,000 files, and I have used FFS to duplicate to my NAS. FFC does this with
no issues and a compare immediately after the sync shows everything equal. The
problematical folder on my D drive contains the same 13,000 files plus another
45 folders with stuff in them. After FFS shows a successful sync i then go to
compare again where it shows 4200 files need to have attributes changed
(copied left to right) whereby when I try nothing happens as per the first
post. One folder syncs perfectly to the NAS but the other doesnt? Sorry to
post such a long message but just want to be clear. Thanks
I have a folder on my D drive of my win 7 32bit home p pc that contains about
13,000 files, and I have used FFS to duplicate to my NAS. FFC does this with
no issues and a compare immediately after the sync shows everything equal. The
problematical folder on my D drive contains the same 13,000 files plus another
45 folders with stuff in them. After FFS shows a successful sync i then go to
compare again where it shows 4200 files need to have attributes changed
(copied left to right) whereby when I try nothing happens as per the first
post. One folder syncs perfectly to the NAS but the other doesnt? Sorry to
post such a long message but just want to be clear. Thanks
-
- Site Admin
- Posts: 7211
- Joined: 9 Dec 2007
FFS employs comprehesive error reporting, namely all(!) low level system calls
are checked. If FFS succeeds with synchronization and did not report any
errors, although not everything was done as expected, this is due to poorly
implementation of the underlying device or network drivers. This is
unfortunate, but can actually happen, as seen for some cloud storages and
network drives.
It seems the situation you describe is just like that. In any case, a few
screenshots showing this behavior may be beneficial. In particular I'd be
interested in the exact difference that triggers the category "changed
attribute" after the first seemingly successful sync.
are checked. If FFS succeeds with synchronization and did not report any
errors, although not everything was done as expected, this is due to poorly
implementation of the underlying device or network drivers. This is
unfortunate, but can actually happen, as seen for some cloud storages and
network drives.
It seems the situation you describe is just like that. In any case, a few
screenshots showing this behavior may be beneficial. In particular I'd be
interested in the exact difference that triggers the category "changed
attribute" after the first seemingly successful sync.
- Posts: 21
- Joined: 17 Jul 2011
Hi, thanks again for responding. This unusual behavior occurred immediately
after upgrading to the latest version. I have tried an experiment, I copied
(overwrite) with teracopy all 52,000 files from my D drive to the nas box,
which took about 4 hours. Now when I do a compare everything shows identical.
I do very much appreciate the effort thats gone into this software, and my
intention is not to run it down. I have been using this PC and NAS for some
time, but for whatever reason this is different behavior. Unfortunately I cant
now give you a screenshot of the problem because teracopy fixed it???????
after upgrading to the latest version. I have tried an experiment, I copied
(overwrite) with teracopy all 52,000 files from my D drive to the nas box,
which took about 4 hours. Now when I do a compare everything shows identical.
I do very much appreciate the effort thats gone into this software, and my
intention is not to run it down. I have been using this PC and NAS for some
time, but for whatever reason this is different behavior. Unfortunately I cant
now give you a screenshot of the problem because teracopy fixed it???????
-
- Site Admin
- Posts: 7211
- Joined: 9 Dec 2007
I'm currently solving a few problems on NAS shares related to this ticket:
[404, Invalid URL: https://sourceforge.net/tracker/?func=detail&atid=1093080&aid=3353929&group_id=234430]
I fixed two problems copying file times with certain access rights and read-
only attributes in v3.19. However the symptoms were the inverse of what you
describe, namely FFS shows error messages which in fact can be avoided.
Maybe we should try this again with the newest release candidate. I'll attach
it to the tracker item above once it's ready. Chances are good this will be
today.
[404, Invalid URL: https://sourceforge.net/tracker/?func=detail&atid=1093080&aid=3353929&group_id=234430]
I fixed two problems copying file times with certain access rights and read-
only attributes in v3.19. However the symptoms were the inverse of what you
describe, namely FFS shows error messages which in fact can be avoided.
Maybe we should try this again with the newest release candidate. I'll attach
it to the tracker item above once it's ready. Chances are good this will be
today.
