I am using Prismo PFO Private Folders that can be encrypted and mapped this to a drive letter. This seems to work fine and I can copy, rename and edit files in this mapped drive.
For some reason FFS only half works hen backing up to this mapped drive. Rather than renaming the temporary file ".ffs_tmp" to the correct name, each directory is left with files of the right size and date/time with the extension of ffs_tmp.
Given that the Private Folder works for other applications, and FFS can clearly write to this mapped drive/folder, is there any specific reason why FFS can't/doesn't rename these files?
I have not tried this for earlier versions of FFS. I notice the build date of 6.4 is April 1st, is this significant? :-)
ffs_tmp files not being renamed by FFS 6.4
- Posts: 2
- Joined: 28 Feb 2013
-
- Site Admin
- Posts: 7281
- Joined: 9 Dec 2007
Hm, looks like a bug in Private Folder to me. Similarly as I wrote in another post that FFS does not copy files, FFS neither renames files. FFS simply calls the Windows routine to let it handle the renaming. This routine internally redirects to the driver level code.
If you see no error message, this means that FFS did not get any error back from Windows. Assuming that Windows code can be expected to be pretty much error-free for such a fundamental operation as renaming files, this suggests a bug in the "Prismo PFO Private Folders" drivers of the kind "silent failure".
Anyway I'll try to get my hands at this program and see if I can reproduce the behavior.
> April 1st, is this significant? :-)
No, FFS actually tries to behave like a serious application and not do april fool's jokes :D The only thing non-serious is the construction worker in the progress dialog - which some user's don't like - maybe they're right and FFS would look more professional without.
If you see no error message, this means that FFS did not get any error back from Windows. Assuming that Windows code can be expected to be pretty much error-free for such a fundamental operation as renaming files, this suggests a bug in the "Prismo PFO Private Folders" drivers of the kind "silent failure".
Anyway I'll try to get my hands at this program and see if I can reproduce the behavior.
> April 1st, is this significant? :-)
No, FFS actually tries to behave like a serious application and not do april fool's jokes :D The only thing non-serious is the construction worker in the progress dialog - which some user's don't like - maybe they're right and FFS would look more professional without.
- Posts: 2
- Joined: 28 Feb 2013
You could well be correct that this is more a Prismo issue.
When I deleted files within the mounted folder I got a number of errors that I haven't seen anywhere else. I don't recall the error number, but other people with this error had corrupted partitions on their drives, so confirming this is most likely a Prismo issue.
While not a compressed private folder, I have moved onto TruCrypt and so far so good.
Many thanks for looking into this.
Regarding the progress dialogue, I do feel some indication of progress is useful though it does seem to dance around a lot! I've just seen it change from 7 hours to 30 days and back again!
When I deleted files within the mounted folder I got a number of errors that I haven't seen anywhere else. I don't recall the error number, but other people with this error had corrupted partitions on their drives, so confirming this is most likely a Prismo issue.
While not a compressed private folder, I have moved onto TruCrypt and so far so good.
Many thanks for looking into this.
Regarding the progress dialogue, I do feel some indication of progress is useful though it does seem to dance around a lot! I've just seen it change from 7 hours to 30 days and back again!
-
- Site Admin
- Posts: 7281
- Joined: 9 Dec 2007
Just tested: I get a lot of temporary errors like:
Cannot move file
"C:\folder\file.txt.ffs_tmp" to
"C:\folder\file.txt".
Error Code 87: Falscher Parameter. (MoveFileEx)
Pressing "retry" makes the operation succeed.
Looking at the Process Monitor log it becomes clear that occasionally Prismo rejects Windows system calls with "INVALID PARAMETER" for no apparent reason while the very same calls with identical parameters succeed if repeated only a short time slice later. Prismo apears to have a problem with the speed of FFS issuing system calls since the problem above can only be reproduced during synchronization and not manually e.g. via Explorer or when the users presses "retry" in FFS, slowing down the pace.
The same problem ("INVALID PARAMETER") occasionally occurs for file deletion which leads to remnant .ffs_tmp files as described above.
Analysis: Looks like a quality of implementation issue with Prismo which do not seem to have tested their software und harder conditions other than users manually invoking file operations via Explorer.
Cannot move file
"C:\folder\file.txt.ffs_tmp" to
"C:\folder\file.txt".
Error Code 87: Falscher Parameter. (MoveFileEx)
Pressing "retry" makes the operation succeed.
Looking at the Process Monitor log it becomes clear that occasionally Prismo rejects Windows system calls with "INVALID PARAMETER" for no apparent reason while the very same calls with identical parameters succeed if repeated only a short time slice later. Prismo apears to have a problem with the speed of FFS issuing system calls since the problem above can only be reproduced during synchronization and not manually e.g. via Explorer or when the users presses "retry" in FFS, slowing down the pace.
The same problem ("INVALID PARAMETER") occasionally occurs for file deletion which leads to remnant .ffs_tmp files as described above.
Analysis: Looks like a quality of implementation issue with Prismo which do not seem to have tested their software und harder conditions other than users manually invoking file operations via Explorer.
