# 无法挂载EFS文件系统：资源暂时不可用

- **ID:** `cloud/gcp-cloud-run-efs-mount-missing`
- **领域:** cloud
- **类别:** runtime_error
- **错误码:** `EFSMountError`
- **验证级别:** ai_generated
- **修复率:** 78%

## 根因

Cloud Run服务无法挂载EFS文件系统，因为VPC连接器配置错误或EFS挂载目标位于不同子网且缺少正确路由。

## 版本兼容性

| 版本 | 状态 | 引入 | 弃用 |
|------|------|------|------|
| Cloud Run (managed) gcloud 450.0.0 | active | — | — |
| AWS EFS (via VPC connector) | active | — | — |

## 解决方案

1. ```
   Verify the VPC connector is in the same VPC and subnet as the EFS mount target. Use `gcloud compute networks vpc-access connectors describe CONNECTOR_NAME` to check network configuration. Then ensure the EFS security group allows inbound NFS (port 2049) from the VPC connector's CIDR.
   ```
2. ```
   Add a VPC connector with a static IP range that overlaps the EFS mount target subnet. Example: `gcloud compute networks vpc-access connectors create my-connector --region us-central1 --network default --range 10.8.0.0/28`
   ```

## 无效尝试

- **Increase Cloud Run memory limit** — Memory limit does not affect NFS mount availability; the error is network-related. (60% 失败率)
- **Recreate the EFS file system** — The file system itself is healthy; the issue is in the network path between Cloud Run and EFS. (80% 失败率)