在Perforce（P4V）中，我试图删除一个工作区，但是出现一个错误，说明文件系统P4Root没有足够的空间
确切的错误消息显示文件系统“ P4Root”仅免费1.9克，但是服务器配置至少需要2G可用。
我试图删除我偶然制作的新工作空间，但要遇到此错误，P4V现在不会让我做任何事情，包括删除似乎引起问题的工作空间。我该如何解决？
the exact error message says The filesystem 'P4ROOT' has only 1.9G free, but the server configuration requires at least 2G available.
I am trying to delete a new workspace i made by accident but keep getting this error, P4V now wont let me do anything, including deleting this workspace that seems to be causing the issue. How do i fix this?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
p4root在服务器上，因此，如果您连接到远程服务器，则需要联系该服务器的管理员，并让他们知道它是楔形的。特别是您的工作区不是问题，服务器上的总体缺乏空间。修复它的所有需要碰到的就是增加可用的磁盘空间。 （删除工作空间可以通过修剪相关的DB条目来释放远程服务器上的 Little 空间，但是与仓库文件相比，这些条目非常小。默认服务器在启动任何操作之前先寻找可用的2GB空白空间。这是为了提供合理的保证，即在操作过程中它不会完全耗尽空间，因为实际上很难从硬性限制中恢复（db表可能处于部分编写的状态等）。
如果管理员想尝试通过消除大文件来解决此问题（这通常是痛苦的，我建议只是为问题扔更大的硬盘驱动器），他们可以暂时降低该阈值以便能够运行闭塞性，但我建议之后碰到它。
P4ROOTis on the server, so if you're connecting to a remote server, you need to contact the admin of that server and let them know that it's wedged. Your workspace specifically is not the problem, the overall lack of space on the server is. All that needs to happen to fix it is increasing the available disk space. (Deleting your workspace would free up a little space on the remote server by pruning the associated db entries, but those are very small compared to the depot files.)The "requires 2G available" thing is because by default the server looks for an available 2GB of empty space before it starts any operation; that's to provide reasonable assurance that it won't run out of space completely during the operation, since actually hitting a hard limit can be hard to recover from (db tables might be in a partially-written state, etc).
If the admin wants to try fixing this by obliterating large files (this is usually a pain and I'd recommend just throwing a bigger hard drive at the problem instead), they can temporarily lower that threshold to be able to run the obliterate, but I'd recommend bumping it back afterwards.