Recycle Bin iterative Directory stack

Get help for specific problems
Posts: 2
Joined: 24 Apr 2014

sefiro

Cloned a SSD to a HDD for a hot backup drive. Been using FFS to keep the hot backup
current. On the backup drve (F drive), found a number of directories with a iteratve
subdirectory looking like the following:

F:\RecycleBin.ffs_tmp\RecycleBin_2.ffs_tmp\RecycleBin_1.ffs_tmp\RecycleBin.ffs_tmp\Recycle
Bin_2.ffs_tmp\RecycleBin_1.ffs_tmp\. . . . . . . .

Besides taking up space, it's time consuming to remove the left over directories as W8
reports the root file names to be too long and so it won't allow deletion. I've been
renaming the folder names to single letter names to get the root name down to a size the
OS will allow for deletion.

What are these? What did I do wrong in setting up the sync rules? The sync rules are
basic with just exclusions (i.e. pagefile,)?

I've attached the log from the last sync.
Attachments
alternate.html
(3.42 KiB) Downloaded 110 times
LastSyncs.log
(97.98 KiB) Downloaded 94 times
User avatar
Site Admin
Posts: 7282
Joined: 9 Dec 2007

Zenju

> W8 reports the root file names to be too long

FFS doesn't have the 260-character path restriction so you can delete long paths manually via the main dialog.

> What are these? What did I do wrong in setting up the sync rules?

RecycleBin.ffs_tmp is just a temp directory where files are collected before they are moved to the recycle bin as a single fast batch operation.

For some reason FFS did not have the rights to delete the "RecycleBin.ffs_tmp" folder after use. So the next sync created a new one "RecycleBin_1.ffs_tmp" and tried to clean-up the old temp directory that is still there, etc.
This looks like a NTFS permission issue where the FFS process has rights to create a folder but not to delete it.
Posts: 2
Joined: 24 Apr 2014

sefiro

Tried the main dialog, was able to delete some additional files with it but it too stopped. Had to manually move directories to root and delete. Deleted about 100G of accumulated files - estimated to be ~200+ directories deep - all with the RecycelBin.ffs*_tmp folders. Found a couple of files with system or administrator access requirements and moved them out of the directory. A good 3 hours of work - for a sync that has been running for 6 weeks at 24x/day.

Have upgrade to 6.4 and ran a couple of manual syncs to see if anything repeated. Nothing so far.

We'll check back in a couple of weeks
Posts: 1
Joined: 2 Sep 2014

saammh

Place the attached file in the 'root' RecycleBin.ffs_tmp folder.
double-click it

It renames the RecycleBin.ffs_tmp inside the previous one, move it one level lower and deletes the previous one and its content, then again and again.
Attachments
00.cmd
(148 Bytes) Downloaded 117 times
Posts: 1
Joined: 21 Jan 2015

simonkeating

I have the same problem. I tried scanning the directory tree with FFS but it gave up after finding 4251 items and throwing an error "1130: Not enough server storage is available to process this command. (readDir)"

The 00.com batch file in the thread above doesn't work for me.

Any other ideas?
Attachments
Capture.PNG
Capture.PNG (56.99 KiB) Viewed 955 times
User avatar
Site Admin
Posts: 7282
Joined: 9 Dec 2007

Zenju

The problem with recursive creation of temporary recycle bin directories has been fixed for the next release:
[404, Invalid URL: https://freefilesync.org/FreeFileSync_7.3_beta_Windows_Setup.exe]