locked
2.1 problems with copying files to destination. RRS feed

  • Question

  • Hello,

    I installed Synctoy 2.1 and tried it out.
    It synced a lot of files to destination but some files failed, then I tried again after a reboot then some of the failed actions succeeded.  But now I have a bunch of these (more than the log, it's shortened) that will not sync to the destination.
    It says that there is not enough space on destination but that is not true, there are more than 100GB free and a manual copy operation works just fine to the exact same destination.

    SYNC: 11/18/2009 11:26:05:854: Started scanning directory : C:\Private\Dokument\
    SYNC: 11/18/2009 11:26:05:854: Started scanning directory : \\192.168.137.185\mnt\1500\.sync\Dokument\
    SYNC: 11/18/2009 11:26:07:539: Stopped scanning directory : C:\Private\Dokument\
    SYNC: 11/18/2009 11:26:08:428: Stopped scanning directory : \\192.168.137.185\mnt\1500\.sync\Dokument\
    SYNC: 11/18/2009 11:26:08:631: Preview of Dokument (C:\Private\Dokument\, \\192.168.137.185\mnt\1500\.sync\Dokument\) in time 00:00:02:776.
    SyncToy action was 'Echo'
    Found 38 actions to perform.
    Found 9 304 files that did not require action.
    Analyzed 3 350,6 files per second.
    Avoided copying 3 878 611 568 bytes in 9 304 files.
    Saved approximately 02:09:17:00 by not copying any files.

    SYNC: 11/18/2009 11:26:09:145: SyncToy run of Dokument (C:\Private\Dokument\, \\192.168.137.185\mnt\1500\.sync\Dokument\) completed at 2009-11-18 11:26:09.
    SyncToy action was 'Echo'.
    SyncToy options were:
    Active for run all
    All files included
    No files excluded
    Do not check file contents
    Include read-only files
    Include hidden files
    Include system files
    Backup older files (send to Recycle Bin)
    All subfolders included
    SyncToy run took 00:00:00:499.
    Copied 1 333 617 858 bytes in 38 files in 00:00:00:499.
    Bytes per second 2 671 510 132,2, files per second 76,1.
    Avoided copying 3 878 611 568 bytes in 9 304 files that did not require action.
    Saved approximately 00:00:01:452 by not copying all files.
    Warning: 38 failures occured.
    You can retry by selecting "Run" again or select "Preview" to see
    the operations that remain to be performed.

    SYNC: 11/18/2009 11:26:09:145: *** Error: Cannot write to the destination file. There is not enough space on the disk. (Exception from HRESULT: 0x80070070) Copying C:\Private\Dokument\plugg osort & pågående\plugg.osorterat\Whizky_74822633.rar to \\192.168.137.185\mnt\1500\.sync\Dokument\plugg osort & pågående\plugg.osorterat\Whizky_74822633.rar

    Error: Cannot write to the destination file. There is not enough space on the disk. (Exception from HRESULT: 0x80070070) Copying C:\Private\Dokument\plugg osort & pågående\plugg\Management\Nya Perspektiv på organisation och ledarskap\orginal bilder.rar to \\192.168.137.185\mnt\1500\.sync\Dokument\plugg osort & pågående\plugg\Management\Nya Perspektiv på organisation och ledarskap\orginal bilder.rar

    Error: Cannot write to the destination file. There is not enough space on the disk. (Exception from HRESULT: 0x80070070) Copying C:\Private\Dokument\plugg osort & pågående\plugg\Management\Nya Perspektiv på organisation och ledarskap\Nya Perspektiv på organisation och ledarskap.pdf to \\192.168.137.185\mnt\1500\.sync\Dokument\plugg osort & pågående\plugg\Management\Nya Perspektiv på organisation och ledarskap\Nya Perspektiv på organisation och ledarskap.pdf

    Error: Cannot write to the destination file. There is not enough space on the disk. (Exception from HRESULT: 0x80070070) Copying C:\Private\Dokument\XP dokument\KMP_293_1417_beta.exe to \\192.168.137.185\mnt\1500\.sync\Dokument\XP dokument\KMP_293_1417_beta.exe

    Error: Cannot write to the destination file. There is not enough space on the disk. (Exception from HRESULT: 0x80070070) Copying C:\Private\Dokument\XP dokument\StarCraft_II_Fansite_Kit_EN_GB.zip to \\192.168.137.185\mnt\1500\.sync\Dokument\XP dokument\StarCraft_II_Fansite_Kit_EN_GB.zip

    Error: Cannot write to the destination file. There is not enough space on the disk. (Exception from HRESULT: 0x80070070) Copying C:\Private\Dokument\XP dokument\bleh.reg to \\192.168.137.185\mnt\1500\.sync\Dokument\XP dokument\bleh.reg

    Error: Cannot write to the destination file. There is not enough space on the disk. (Exception from HRESULT: 0x80070070) Copying C:\Private\Dokument\k800i\Update_Service_Setup-2.7.9.14-1.exe to \\192.168.137.185\mnt\1500\.sync\Dokument\k800i\Update_Service_Setup-2.7.9.14-1.exe

    Error: Cannot write to the destination file. There is not enough space on the disk. (Exception from HRESULT: 0x80070070) Copying C:\Private\Dokument\k800i\XS++.rar to \\192.168.137.185\mnt\1500\.sync\Dokument\k800i\XS++.rar

    So is this a bug or another problem?
    Wednesday, November 18, 2009 12:10 PM

Answers

  • I have found the problem
    \\192.168.137.185\ and \\192.168.137.185\mnt\ is less than 100 MB (USB thumb drive)
    \\192.168.137.185\mnt\1500\ is 1500 MB


    So I created a new share, instead of \mnt i added a \mnt\1500 share in samba.
    Then I mapped that share and then synced against the new share, then it worked.

    So SyncToy believed that the old share had 7 MB free when in fact it had like 100 GB free.
    Perhaps next version should not look at the reported sharesize and decide to fail it is to small. It should just try the copy operation first and then fail if the share is full.

    Wednesday, November 18, 2009 8:05 PM

All replies

  • Hi -

    The error is pretty clear about the fact that it is being denied permissions to copy to that location. It looks like you are accessing some share - is it possible that you are hitting some quota restriction on that share? As a sanity check - try deleting some files on both sides and see if the files that are not being copied over are now being sync'ed?

    Thanks
    Deepa
    Deepa ( Microsoft Sync Framework)
    Wednesday, November 18, 2009 6:43 PM
  • Nope no quota, I've tried deleteing files.
    I've tried the limits by uploading more files.
    Copying these files manually works, for instance Copying C:\Private\Dokument\XP dokument\bleh.reg to \\192.168.137.185\mnt\1500\.sync\Dokument\XP dokument\bleh.reg

    So I've verified permission problems, space problems
    It's strange that with Windows explorer it works like a charm, but not with SyncToy.
    Now what?
    • Edited by Raboo Wednesday, November 18, 2009 7:18 PM formatting error
    Wednesday, November 18, 2009 7:16 PM
  • I have found the problem
    \\192.168.137.185\ and \\192.168.137.185\mnt\ is less than 100 MB (USB thumb drive)
    \\192.168.137.185\mnt\1500\ is 1500 MB


    So I created a new share, instead of \mnt i added a \mnt\1500 share in samba.
    Then I mapped that share and then synced against the new share, then it worked.

    So SyncToy believed that the old share had 7 MB free when in fact it had like 100 GB free.
    Perhaps next version should not look at the reported sharesize and decide to fail it is to small. It should just try the copy operation first and then fail if the share is full.

    Wednesday, November 18, 2009 8:05 PM
  • Hi Raboo,

    I have a question. When you were saying “Then I mapped that share and then synced against the new share, then it worked.”, did you mean this approach resolved your problem, or caused your problem?

    If it resolved your problem, would you like to describe how you “mapped that share and then synced against the new share” with more details, please?  Then your experience will help the other users with similar problems.

    Or if that is what caused your problem, we also need more information, so that we can try to help you with a work around. This seems a new scenario for us and will help us to improve the tool.

    Thanks


    This posting is provided "AS IS" with no warranties, and confers no rights.
    Monday, December 7, 2009 6:49 AM
  • Hi -

    Actually SyncToy does not look at reported sharesizes - the error we are reporting is exactly what the Win32 API we were using to copy the file over is reporting back to us when we are going the actual copy.

    Thanks
    Deepa
    Deepa ( Microsoft Sync Framework)
    Tuesday, December 22, 2009 1:44 AM
  • So then why would it work in Windows Explorer, but not with SyncToy? I'm having this issue as well.
    Monday, April 26, 2010 4:43 AM
  • I have been having this same problem I have found out what the issue is. For me at least.

    My remote directory comes from my personal NAS device running Linux, which provides shared directories via samba.

    On my NAS, the root file system is a read-only romfs filesystem. The hdd, which is writable, is mounted on /mnt/disk1

    Now, if I share the root directory (/) as 'root' on the NAS and attempt to use SyncToy to sync to \\mynas\\root\\mnt\\disk1, it fails. If I right-click the root folder and go to properties from Windows, it says:

    Size: 0 bytes

    Size on disk: 0 bytes.

    If however I share /mnt/disk1 directly as 'disk1', and try to Sync to that, everything works fine.

    In short, it seems that SyncToy (or the Win32 API) is assuming that the highest level directory of the remote share will always be the same partition as any folders under it.  It is checking the space available on the top level folder and not the one you are actually asking it to write to. 

     

    Tuesday, July 20, 2010 11:10 PM