I have been doing some testing with P4VFS to investigate how we can utilize it as part of our user syncs. One of the key aspects for us is the ability to re-virtualize any part of a workspace on demand via p4vfs resident -v.

Unlike the sync command, it appears the resident command doesn't support quiet logging? Even after adding the "-q" parameter to the resident command, it presents that it is doing a force|quiet sync but still presents the sync log anyway. (See image below)

This is not ideal as if we are re-virtualizing an entire workspace, the time taken for this grows exponentially if we don't use quiet logging as the resident command will print every file that has been virtually synced to it's #have revision. This takes a while in a large depot.

ServiceListener::SrvConnectToDriver Failed to SrvConnectToDriver [0x0] Retry [1]
ServiceListener::SrvConnectToDriver Failed to SrvConnectToDriver [0x0] Retry [2]
ServiceListener::SrvConnectToDriver Failed to SrvConnectToDriver [0x0] Retry [3]
ServiceListener::SrvConnectToDriver Failed to SrvConnectToDriver [0x0] Retry [4]
ServiceListener::SrvConnectToDriver Failed to SrvConnectToDriver [0x0] Retry [5]
ServiceListener::SrvConnectToDriver Failed to SrvConnectToDriver [0x0] Retry [6]
ServiceListener::SrvConnectToDriver Failed to SrvConnectToDriver [0x0] Retry [7]
ServiceListener::SrvConnectToDriver Failed to SrvConnectToDriver [0x0] Retry [8]

When I download the official installation package, it works fine. However, when I try to install the package generated from compiling the code, it says that some files cannot be found. After I put the Setting.xml file in the same directory, the installation succeeds. Is this reasonable? Has the official installation package already compiled the xml file into the program?

tks.

Hello,
first, thank you for sharing and maintaining p4vfs, it's very cool.

I'd like to ask if there's a way to programmatically query the Size on disk that I can see in the folder properties window. I'd like to know how much space a given p4vfs-managed directory takes on a disk.

I've tried various approaches, but without success. Mentioning some below:

• CMD's dir command reports only the full size
• Git BASH's du command reports the full size and hydrates files in the process
• Sysinternals' du command reports both Size and Size on disk, but the latter is incorrect (there's a non-zero value)
• Python's os.stat(file_path).st_size returns the full size

Best,
Juraj

Performing a perforce sync on files with unicode characters in their names/paths results in incorrect output during sync.

This issue may also affect other file operations.

Tested on both CMD, and PowerShell/Windows Terminal

Sync completes successfully & properly, but output leads users to believe something failed or was incorrect.

When I used the P4V client to create a new workspace and pulled it using P4VFS, I found that the P4VFS driver was offline

I noticed that the file size before and after hydration differs. This causes unexpected things to happen in some cases. For example:

 Volume in drive D is Data
 Volume Serial Number is F24C-78F7

 Directory of d:\FN2\Engine\Source

10/03/2023  09:30               421 UnrealClient.Target.cs
10/03/2023  09:30               448 UnrealEditor.Target.cs
10/03/2023  09:30               463 UnrealGame.Target.cs
10/03/2023  09:30             (455) UnrealServer.Target.cs
               4 File(s)          1,787 bytes

d:\FN2\Engine\Source>more UnrealServer.Target.cs
// Copyright Epic Games, Inc. All Rights Reserved.

using UnrealBuildTool;
using System.Collections.Generic;

[SupportedPlatforms(UnrealPlatformClass.Server)]
public class UnrealServerTarget : TargetRules
{
    public UnrealServerTarget(TargetInfo Target) : base(Target)
        {
                Type = TargetType.Server;
                IncludeOrderVersion = EngineIncludeOrderVersion.Latest;
                BuildEnvironment = TargetBuildEnvironment.Shared;
                ExtraModuleNames.Add("Unreal

d:\FN2\Engine\Source>more UnrealServer.Target.cs
// Copyright Epic Games, Inc. All Rights Reserved.

using UnrealBuildTool;
using System.Collections.Generic;

[SupportedPlatforms(UnrealPlatformClass.Server)]
public class UnrealServerTarget : TargetRules
{
    public UnrealServerTarget(TargetInfo Target) : base(Target)
        {
                Type = TargetType.Server;
                IncludeOrderVersion = EngineIncludeOrderVersion.Latest;
                BuildEnvironment = TargetBuildEnvironment.Shared;
                ExtraModuleNames.Add("UnrealGame");
        }
}

d:\FN2\Engine\Source>dir Unreal*
 Volume in drive D is Data
 Volume Serial Number is F24C-78F7

 Directory of d:\FN2\Engine\Source

10/03/2023  09:30               421 UnrealClient.Target.cs
10/03/2023  09:30               448 UnrealEditor.Target.cs
10/03/2023  09:30               463 UnrealGame.Target.cs
10/03/2023  09:30               471 UnrealServer.Target.cs
               4 File(s)          1,803 bytes
               0 Dir(s)  3,100,296,794,112 bytes free

As you can see, the unhydrated file size is reported as 455 and the hydrated file size is 471. The difference is presumably because p4 stores text files in a normalized form on the server and transcodes it according to client settings as part of the syncing process.

The end result is that in this case more will only do a partial read of the file the first time, but the second time it reads the entire file. Many other processes still function as expected, which I assume means they just keep reading until EOF instead of checking the file size up front.

Experienced an error syncing today on a file with an accent character [specifically é] in its name. Virtual syncs result in a file with a � character in its place. Opening the file results in errors (probably because p4vfs has trouble figuring out the actual file name to force sync).

As a workaround force syncing using the normal p4 method worked fine.

I have used P4VFS on Windows to sync to the latest version of my project (p4vfs sync ...#head). However, I'm using VSCode running under WSL2/Ubuntu-20.04 to edit files. When I try to access the files using VSCode or Ubuntu command line, then I only see zeros in the file:

If I use a native Windows program to read the file, then I can see the actual contents of the file in WSL...

$ od -tx1 SourceCode.cc
0000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*
0213720 00 00 00 00 00 00 00 00 00 00 00
0213733

$ /mnt/c/windows/system32/cmd.exe <<< "type sourceCode.cc" &> /dev/null
$ od -tx1 SourceCode.cc
0000000  2f  2f  20  24  49  64  3a  20  ...
...
0213720  53  74  61  74  65  3b  0a  7d  0a 
0213733

Is it possible to make this run seamlessly under WSL? (i.e. without the need to use a windows native program to trigger P4VFS)?

Note: (I had previously opened this up under Discussion, but think it is more suited to an issue)

Hi, thanks for the awesome work on p4vfs!
I would like to report an issue I had when testing out p4vfs. I found out an solution, but wanted to check if there is a better fix, or if I missed something for my setup.

• Background
  Perforce server is in Unicode mode, Client P4CHARSET is set to utf8.

• Issue
  If a file unicode_test.txt is of unicode filetype on perforce, then following command would fail.
  p4vfs.exe sync -r -f //depot//unicode_test.txt
  And gives the error: - Translation of file content failed near line ...
  The same command in p4 would succeed:
  p4 sync -f //depot//unicode_test.txt
  The same p4vfs command in local mode would also succeed:
  p4vfs.exe sync -r -f -t //depot//unicode_test.txt
  Just in case I attached the file for my test there: UnicodeTest.txt

• Investigation
  By outputing m_P4->m_ClientApi->GetCharset().Text() in FDepotClient::Connect(const DepotConfig& config), I found the issue.
  In p4vfs.exe, the FDepotClient is properly picking up P4CHARSET settings and is set to utf8. However in P4VFS.Service.exe, it does not pick up P4CHARSET, and charset is set to auto. I'm not sure why, but this is the reason we have translation problem using sync command in service mode, but not in local mode.

• Fix
  Added the following in FDepotClient::Connect(const DepotConfig& config)

DepotString charset = GetEnvImpersonated(DepotConstants::P4CHARSET); 
if (charset.empty() == false) 
{ 
    m_P4->m_ClientApi->SetCharset(charset.c_str()); 
} 

Much appreciated if you can share any insight on this problem. Thank you.

I opened the CMD with administrator. Then i set the $P4PORT, $P4CLIENT and $P4USER variable. I run the p4vfs.exe login command and then login to the perforce with password.
I want to sync my debot with p4vfs.exe sync //myprojects/projectname/username/folder/name/... command.
But the p4vfs always crash with sync action:

P4VFS version 1.24.2.0
Virtual Sync: ["//myprojects/projectname/username/folder/name/..."] Normal Atomic @999999
Started at [03/24/2023-17:24:52] version [1.24.2.0]
1 Modification messages to act on.
Unsupported sync action: None <--- ERROR
Virtual Sync Summary:
Total Files: 1 / 1
Total Time: 0 sec (0.656)
Virtual Mod Time: 0 sec
Resident Mod Time: 0 sec
Virtual File Size: 0 bytes
Disk File Size: 0 bytes

and here is my p4vfs.exe info output:
P4VFS version 1.24.2.0
P4 UserName: username
P4 ClientName: p4vfs
P4 ClientHost: DESKTOP999999
P4 ClientRoot: c:\Share
P4 ClientStream:
P4 ServerAddress: perforceip:1999
P4 ServerVersion: P4D/LINUX26X86_64/2021.1/2313999 (2022/07/15)
P4 CaseHandling: sensitive
P4VFS CurrentVersion: 1.24.2.0
P4VFS ServiceVersion: 1.24.2.0
P4VFS DriverVersion: 1.24.0.0
P4VFS DriverReady: True
P4VFS ServiceReady: True
P4VFS SystemReady: True

I tried using p4vfs to populate a large tree, and after a few minutes it terminated with an error:

P4VFS version 1.24.0.0
Virtual Sync: ["XyzGame/..."] Quiet Single @24588784
SocketModelClient.SendCommand exit with exception: One or more errors occurred.

The tree appears to be complete but the fact that the command errored out is a bit concerning. I have not yet looked at the code so don't know how easy it might be to either back out all changes to the file system or add retry/resume logic somehow.

The server log contains the following

-03/10/2023-09:23:18::<Error> - SocketModelLogDevice.WriteDevice exception: One or more errors occurred.
-03/10/2023-09:23:18::<Info> - //Xyz/Main/Engine/Content/Internationalization/EFIGSCJK/icudt64l/lang/en_LR.res#1 - installed as d:\FN2\Engine\Content\Internationalization\EFIGSCJK\icudt64l\lang\en_LR.res
-03/10/2023-09:23:18::<Info> - Aborting Sync from DepotClient fault
-03/10/2023-09:23:18::<Info> - Aborting Sync from DepotClient fault
-03/10/2023-09:23:18::<Info> - Aborting Sync from DepotClient fault
-03/10/2023-09:23:18::<Info> - Aborting Sync from DepotClient fault
-03/10/2023-09:23:18::<Info> - Aborting Sync from DepotClient fault
-03/10/2023-09:23:18::<Info> - Aborting Sync from DepotClient fault
-03/10/2023-09:23:18::<Info> - Aborting Sync from DepotClient fault
-03/10/2023-09:23:18::<Info> - Aborting Sync from DepotClient fault
-03/10/2023-09:23:18::<Error> - SocketModelServer.HandleClientConnection exiting with exception: One or more errors occurred.

When I download the exe from the readme, the installation is successful, but when I compile and install from the source code, the installation fails, and the error is reported:Loading p4vfsflt Driver load FAILED

Is there a way to configure p4altsync to use this version of p4vfs?

https://www.perforce.com/manuals/p4vfs/Content/P4VFS/developer.html

When I used version 1.24.2.0, I found that I could connect to Peforce during debugging, but when I used version 1.26.1.0, I found that I couldn’t connect.

How to Set P4VFS's P4CHARSET

In P4V I can add it as a Custom tool, but if I select Run tool in terminal window, I can see the error logs, but no way to know when it's finished. If I also check Close window upon completion, then I kinda get a clue when it's finished (the window disappears), but then I can't read any errors.

If I don't select Run tool in terminal window, then the output is not visible anywhere, so that's not great either.

Also when using this as a P4V Custom Tool, I couldn't find a way to select just some folders and run p4vfs sync on those. It only shows up in the context menu when I select the workspace root folder. If I add %f or %F to the command line args ( those the only two that are using workspace syntax), then it doesn't show up in the context menu of any folders.

I'd be interested to learn how others integrated this to their workflow.

After I use P4VFS to download a file, the size obtained through the stat function or the size function of the filesystem is wrong，Only after the file is actually downloaded, the obtained size is correct

We very heavily rely on argument files when performing a syncing using p4.exe. It allows us to filter out unnecessary files. When we ported over to p4vfs.exe we continued to use an argument file. However I have recently noticed that they don't always succeed.

The more files to sync, the greater the chance of failure. I cannot tell if there is a safe minimum.

This seems to only occur when using an arguments file. I have not been able to reproduce the issue without an arguments file. sync and populate with an arguments file both have the same issue.

At around 25,000 files I see about a 1/6 success rate.

When it fails I have seen the following:

• Exit code will always be 1
• All files are missing. I have not encountered a partial sync.
• The p4 have table may sometimes be updated
• The error below may sometimes be printed out
• It might fail immediately, or it may first print out all of the files in the arguments file and then after a while fail

SocketModelClient.SendCommand exit with exception: One or more errors occurred.

I have attached a powershell script that I have been using to verify this. To use this script, you will have to have your p4 environment set up so that executing p4vfs sync would just start a sync.

# Tests p4vfs populate using an argument file to perform the sync
# .\p4vfs-test.ps1 -max 10000 will limit the sync to 10000 files
# .\p4vfs-test.ps1 -nofile will not use an argument file
# .\p4vfs-test.ps1 -sync will use sync instead of populate

p4vfs-test.ps1.txt

Is there a way to compile p4vfs.Cosole through VS2019

If I'm not mistaken this altitude is not in the official altitude documentation:

https://learn.microsoft.com/en-us/windows-hardware/drivers/ifs/allocated-altitudes

Also seems to be between two valid ranges, but outside of both. Is that intended?