My Usage: Synchronizing in both directions local folder (C:\xyz) and folder on network drive (\\192.168.1.123\share\xyz)
Sync works in general fine. When a local folder has been deleted FFS detects it and marks on NAS drive for deleting. After processing sync run the folder disappears from list and no error is displayed. Looks fine.
Problem: The folder has been not really deleted on NAS drive. When starting next sync run the still existing folder is found to be new on NAS and copied back again to local disk.
- deleting this folder in windows file explorer works with same user rights fine.
- deleting on command line ("RD \\.....\.... ") works also.
- manual deleting in FFS (right mouse menu "delete") also works not. But no error shows up.
- FFS does all other sync jobs correct but not removing folder on NAS side
- no error reported
This effect is here any time reproduceable.
System is 64bit Win7. NAS is a very small Ethernet-Interface with one USB port for USB-drives.
Not sure if it is a bug in FFS or a problem with OS or network - but anyway shouldn't FFS report an error when deleting fails?
Unable to delete folder on network drive
- Posts: 3
- Joined: 13 Aug 2010
-
- Site Admin
- Posts: 7281
- Joined: 9 Dec 2007
Which version of FFS are you using? Does the file you are trying to delete have a special name or some other attribute that distinguishes it from the other files that FFS does delete successfully?
Are you able to log a process monitor trace (https://technet.microsoft.com/de-de/sysinternals/bb896645.aspx) when trying to delete a file manually in FFS that shows the described problem?
Are you able to log a process monitor trace (https://technet.microsoft.com/de-de/sysinternals/bb896645.aspx) when trying to delete a file manually in FFS that shows the described problem?
- Posts: 3
- Joined: 13 Aug 2010
- Version 5.14 (x64)
- Files are never a problem, only directories (also empty)
- Depends not on names or special pathes. Also with any short simple folder names in root.
I try to create a monitor trace. For privacy reasons i will directly send to your email address.
- Files are never a problem, only directories (also empty)
- Depends not on names or special pathes. Also with any short simple folder names in root.
I try to create a monitor trace. For privacy reasons i will directly send to your email address.
- Posts: 3
- Joined: 13 Aug 2010
Up to now i could not find the root cause. So i am very interested if any other user experienced the same behavior: No error - but not deleted. If so what file system, device and operating system you are using? In some way [my] NAS seems to be treated different by Windows than local drives....
