unable to delete ffs created directories

Get help for specific problems
Posts: 2
Joined: 24 Jun 2012

redparked

ffs 5.2, win2000 sp4
i am unable to delete the directories that ffs creates (like FFS 2012-04-09
114156)
User avatar
Site Admin
Posts: 7279
Joined: 9 Dec 2007

Zenju

What do you mean with "unable"?
Posts: 2
Joined: 24 Jun 2012

redparked

sorry for the delayed response and the sketchy initial report. i've
now solved my problem, but still have a couple of questions based on
the following behavior.

running on win 2000 pro sp4, at the end of a sync with a networkes xp x64
pro, would often report that it was unable to deleted a directory with
a name similar to "FFS 2012-06-26 000729". thus over the past couple
of months i've accumulated two or three dozen "FFS ..." directories.

question 1: does ffs ordinarily delete these directories at the end of
a sync session?

i would try from time to time to delete them (more precisely, move
them to trash), and it would always report an error: access denied. i
even tried to delete them in safe mode, before running anything other
than explorer. no go.

question 2: any idea what is keeping explorer from deleting the FFS
directories? (cygwin ls reports them all to be rwx by everyone, for
whatever that's worth.)

my solution, subsequent to my forum post earlier this week, is to use
cygwin rm to remove them "rm -Rf "FFS*" does the trick.

question 3: is this all expected behavior?
User avatar
Site Admin
Posts: 7279
Joined: 9 Dec 2007

Zenju

> does ffs ordinarily delete these directories at the end of a sync session?
Yes, but it doesn't delete them, but moves them to the recycler. It also
reports failure to do so via an error message. Unfortunately there is no error
code to show on 2000 as this requires Windows Vista and later.

> any idea what is keeping explorer from deleting the FFS directories
Maybe some of the files contained hit the 260 MAX_PATH limit of their full
path. Or there is some strange NTFS permissions thing going on. FFS creates
these temp folders with no extra special settings, just a pure and simple
"CreateDirectory()". Or there is some problem with the recycler on this
volume.

> is this all expected behavior?
Expected is of course no hassle for the user. Normally you would never see
those temp directories after sync has finished.