-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How does p4vfs work with P4 Client correctly #54
Comments
Hi alexjingsi, It's often surprising to find which process may try to hydrate the file first. It's no uncommon to see Windows Defender service (MsSense.exe) read the file in search for possible malware. You can look at the P4VFS.Service logs ("%PUBLIC%\Public Logs\P4VFS\P4VFS.Service") to inspect the process ID which hydrated the file. You can also use the p4vfs monitor application in the task tray P4VFS service does have an
Regards |
Hi @jessk-msft ,
Could you provide some suggestions for the following questions? Q1: If you want to use the p4vfs function, should you completely abandon the use of "p4v client" and instead use p4vfs.exe directly to perform all p4 operations? So as to avoid the accidental restoration of hydrated files by p4v? Q2: Through "p4vfs resident -v ", or "p4vfs sync -v ", local files can be changed to hydrated state, but they will be automatically restored when read again, and they are no longer virtual files. Is it possible to mark the file as hydrated only, but at the same time keep the actual file size, instead of changing the disk size to 0, so that the latest version can be avoided only when updating, without affecting its reading when it is not updated. Regards |
Hi alexjingsi, Q1. I think it's essential to be able to mix-n-match syncing form P4V, p4.exe and p4vfs.exe. Simply consider that syncing from p4vfs would typically be a virtual sync (download file contents on demand), while a sync from P4V "Get Latest version" will be immediate file download. I'd expect "Get Latest version" to overwrite a earlier revision of a virtual sync'd file, without first hydrating the old revision. Q2. A virtual file should be reporting a correct non-zero file size, and zero disk size. There can be a slight discrepancy when it's a "text" type file, in which case the sync I hope that helps. |
When I Installed p4vfs service, and rehydrating some files, their size becomes 0, but it seems that just a refresh operation from the p4 client will trigger IO to read the complete file, causing these files to be re-downloaded. How can I correctly cooperate with the P4 client to avoid unexpected dewatering?
The text was updated successfully, but these errors were encountered: