Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Halaman ini memberikan informasi pemecahan masalah untuk membantu mengatasi masalah yang mungkin Anda
alami saat mencoba memasang atau melepas pemasangan berbagi di instance Filestore.
VM atau pod GKE saya tidak dapat mengakses Filestore
Pastikan apakah instance Filestore dapat dijangkau (ping dan
traceroute tidak didukung) dengan menjalankan:
sudo showmount -e <filestore-ip>
Perintah akan merespons dengan daftar sistem file yang diekspor. Kemudian, periksa
apakah klien dapat menjangkau informasi RPC Filestore dengan
menjalankan:
sudo rpcinfo -p <filestore-ip>
Jika instance Filestore tidak dapat dijangkau, penyebab umum meliputi
setelan jaringan atau setelan ACL yang tidak dikonfigurasi dengan benar, atau Anda mencoba
memasang instance yang salah.
Jika Anda menemukan nfsExportOptions tercantum, periksa apakah alamat IP klien Anda berada dalam salah satu rentang yang tercantum di bagian ipRanges untuk accessMode yang diharapkan.
Jika tidak, Anda harus
mengedit Opsi Ekspor NFS.
Tidak dapat memasang berbagi file ke App Engine
Filestore tidak mendukung App Engine.
Tidak dapat memasang berbagi file dari cluster GKE
Anda tidak dapat langsung memasang fileshare Filestore ke
cluster GKE. Sebagai gantinya, Anda harus
mengonfigurasi PV dan PVC.
Tidak dapat terhubung ke berbagi file yang terpasang saat menggunakan VPN dengan ketersediaan tinggi (HA) atau Cloud Interconnect
Jika Anda menggunakan VPN dengan ketersediaan tinggi (HA) atau Cloud Interconnect dan memasang berbagi file ke VM klien yang menjalankan kernel Linux versi 5, tetapkan opsi pemasangan nconnect ke 1. Setelan ini mencegah beberapa koneksi ke node backend Filestore yang berbeda dan memastikan koneksi ke berbagi file yang dipasang.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-04 UTC."],[[["\u003cp\u003eThis guide offers solutions for troubleshooting issues when mounting or unmounting a share on a Filestore instance.\u003c/p\u003e\n"],["\u003cp\u003eIf a VM or GKE pod cannot access Filestore, ensure the instance is reachable via the \u003ccode\u003eshowmount\u003c/code\u003e and \u003ccode\u003erpcinfo\u003c/code\u003e commands, and verify network and access control list (ACL) settings, including checking for IP-based access restrictions and proper firewall configuration.\u003c/p\u003e\n"],["\u003cp\u003eIf receiving a "permission denied" error when mounting a file share, use the \u003ccode\u003egcloud filestore instances describe\u003c/code\u003e command to confirm if NFS Export Options are configured and if the client's IP address falls within the permitted \u003ccode\u003eipRanges\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eDirect mounting of Filestore file shares is not supported on App Engine, and GKE clusters require the use of a Persistent Volume (PV) and a Persistent Volume Claim (PVC) instead of direct mounts.\u003c/p\u003e\n"]]],[],null,["# Troubleshoot mounting issues\n\nThis page provides troubleshooting information to help address issues you might\nencounter while attempting to mount or unmount a share on a Filestore\ninstance.\n\nMy VM or GKE pod can't access Filestore\n---------------------------------------\n\nConfirm whether the Filestore instance is reachable (`ping` and\n`traceroute` are not supported) by running: \n\n sudo showmount -e \u003cfilestore-ip\u003e\n\nThe command should respond with a list of exported file systems. Then check\nwhether the client can reach Filestore's RPC information by\nrunning: \n\n sudo rpcinfo -p \u003cfilestore-ip\u003e\n\nIf the Filestore instance is not reachable, common causes include\nimproperly configured network settings or ACL settings, or you are attempting to\nmount the wrong instance.\n\n1. Check whether IP-based access control is enabled and check whether the IP address of the client is restricted. For more information, see [Permission denied when trying to mount a file share](#permission-denied-when-mounting).\n2. Check your firewall settings to make sure that the required ports are open. For details, see [Configuring firewall rules](/filestore/docs/configuring-firewall).\n3. If you're trying to access Filestore from a GKE cluster, and are getting the error `mount.nfs: access denied by server while\n mounting ...`, see [Unable to access file share from GKE clusters](/filestore/docs/gke-access-issues).\n\nPermission denied when trying to mount a file share\n---------------------------------------------------\n\nConfirm whether there are any\n[NFS Export Options](/filestore/docs/access-control#ip-based_access_control)\nlisted for the instance: \n\n gcloud filestore instances describe \u003cvar translate=\"no\"\u003einstance-id\u003c/var\u003e \\\n --zone=\u003cvar translate=\"no\"\u003ezone\u003c/var\u003e\n\nwhere:\n\n- \u003cvar translate=\"no\"\u003einstance-id\u003c/var\u003e is the instance ID of the Filestore.\n- \u003cvar translate=\"no\"\u003ezone\u003c/var\u003e is the zone where the Filestore instance resides.\n\nThe command returns something similar to: \n\n```bash\ncreateTime: '2019-10-11T17:28:23.340943077Z'\nfileShares:\n- capacityGb: '1024'\n name: vol1\n nfsExportOptions:\n - accessMode: READ_WRITE\n ipRanges:\n - 128.0.0.0/29\n squashMode: NO_ROOT_SQUASH\nname: projects/yourproject/locations/us-central1-c/instances/nfs-server\nnetworks:\n- ipAddresses:\n - 10.0.0.2\n modes:\n - MODE_IPV4\n network: default\n reservedIpRange: 10.0.0.0/29\nstate: READY\ntier: BASIC_HDD\n```\n\nIf you find `nfsExportOptions` listed, check if the IP address of your client is\nwithin one of the ranges listed under `ipRanges` for the expected `accessMode`.\nIf it isn't, you must\n[edit the NFS Export Options](/filestore/docs/editing-instances).\n\nUnable to mount a file share to App Engine\n------------------------------------------\n\nFilestore does not support App Engine.\n\nUnable to mount a file share from a GKE cluster\n-----------------------------------------------\n\nYou cannot directly mount Filestore file shares to\nGKE clusters. Instead, you must\n[configure a PV and a PVC](/filestore/docs/csi-driver).\n\nCan't connect to mounted file shares when using HA VPN or Cloud Interconnect\n----------------------------------------------------------------------------\n\nIf you use HA VPN or Cloud Interconnect and mount the file share to\na client VM that's running Linux kernel version 5, set the [`nconnect` mount option](https://man7.org/linux/man-pages/man5/nfs.5.html) to `1`. This setting prevents multiple connections to different Filestore backend nodes and ensures connection to mounted file shares. \n\n mount -o nconnect=1"]]
