mirror of
https://github.com/facebook/sapling.git
synced 2024-10-10 16:57:49 +03:00
34edb7b618
Summary: On Windows, the GUID of the mount point identifies the virtualization instance, that GUID is then propagated automatically to the created placeholders when these are created as a response to a getPlaceholderInfo callback. When the placeholders are created by EdenFS when invalidating directories we have to pass GUID. The documentation isn't clear about whether that GUID needs to be identical to the mount point GUID, but for a very long time these have been mismatching due to the mount point GUID being generated at startup time and not re-used. One of the most common issue that users have reported is that sometimes operations on the repository start failing with the error "The provider that supports file system virtualization is temporarily unavailable". Looking at the output of `fsutil reparsepoint query` for all the directories from the file that triggers the error to the root of the repositories, shows that one of the folder and its descendant don't share the same GUID, removing it solves the issue. It's not clear to me why this issue doesn't always reproduce when restarting EdenFS, but a simple step that we can take to solve this is to always re-use the GUID, and that hopefully will lead to the GUID always being the same and the error to go away. Reviewed By: fanzeyi Differential Revision: D25513122 fbshipit-source-id: 0058dedbd7fd8ccae1c9527612ac220bc6775c69 |
||
|---|---|---|
| .. | ||
| test | ||
| __init__.py | ||
| check_filesystems.py | ||
| check_hg.py | ||
| check_kerberos.py | ||
| check_os.py | ||
| check_redirections.py | ||
| check_rogue_edenfs.py | ||
| check_stale_mounts.py | ||
| check_watchman.py | ||
| problem.py | ||