17.00.91 I couldn't create a largish .pa in a subfolder in my GoogleDriveSync folder and things went weird. Repeatable on my PC.

Brian Gregory

I couldn’t create a largish .pa in a subfolder in my GoogleDriveSync folder. I right click on a subsubfolder and choose “Compress to subfolder.pa”. I’m expecting a .pa file somewhere in the region of 15MB in size. However PA halts with an error saying it doesn’t have access and leaves an unfinished .pa file and a .pa.tmp file. One of them, if I remember right the .pa file proves very difficult to delete. I went in to safe mode in the end and then I could delete it. I’ll try and investigate further soon.

spwolf

@brian-gregory interesting… maybe gdrive is trying to sync the file and then PA cant access it?

spwolf

@Mili can check it out…

Mili

Have been trying to reproduce the error, but works every time. A 20MB .PA archive created out of a subfolder in GoogleDriveSynch folder, is created properly.

Was this a one time issue for you @Brian-Gregory or happens every time?

Brian Gregory

Okay wait for me to investigate further.
Fails every time on my PC, but there is loads of other stuff install that might be interacting.
Seems like what I said about being unable to delete the file was wrong too, it deletes fine if you wait a while.

Mili

if it’s a certain type of file, or maybe it is in use, let us know. we’ll try with a scenario as similar as yours

thanks again!

Brian Gregory

Still seen here with .92. It seems to be only when the .tmp file is created as well as the .pa file. It also seems more likely to happen when the directory being compressed is larger. Originally the directory was about 45MB of file and with Google Drive Sync (Now Backup and Sync from Google) disabled the result was an about an 18MB .pa file. But I think it’s more likely to happen if you use larger sizes. I was using Optimize Strong and Ultra.

spwolf

@brian-gregory said in 17.00.91 I couldn't create a largish .pa in a subfolder in my GoogleDriveSync folder and things went weird. Repeatable on my PC.:

Still seen here with .92. It seems to be only when the .tmp file is created as well as the .pa file. It also seems more likely to happen when the directory being compressed is larger. Originally the directory was about 45MB of file and with Google Drive Sync (Now Backup and Sync from Google) disabled the result was an about an 18MB .pa file. But I think it’s more likely to happen if you use larger sizes. I was using Optimize Strong and Ultra.

i would guess that google sync takes over the file trying to sync it before it is done. If you go to Add window> Options, and turn off Use current folder as temp, it will use temp folder and copy end result to your google sync folder… that way it should work fine.

Brian Gregory

@spwolf I think the problem is that PA want’s to rename the .tmp file. Why does it work that way, if the .pa file is temporary and the .tmp file is going to be the final archive why not just use the names the other way round?

spwolf

@brian-gregory because tmp file keeps copying into pa files at the end of different compression steps… if you disable same folder for temp in options, it will just copy end result to that folder and you would avoid this issue.

But pretty sure the problem is that google starts syncing (and locking) that file right away, while PA is still being written. Same when I tried to use Outlook pst file in google sync folder, it would cause corruption since it would lock it at the same time when Outlook is using it.

Brian Gregory

@spwolf No that doesn’t make any difference. It still creates both files. It appears to do one step into the .pa file copy it to the .tmp file do another bit in the .pa file append to the .tmp file etc and at the end delete the .pa and rename the .tmp to .pa.

spwolf

@brian-gregory it should be in temp folder… @mili will log it in.