We are using multiple pods to access the same PVC/PV with subPath mounting. During usage, we noticed that in one of the pods, after creating a new file in the subPath mount, the file is initially visible when using the ls command, but after a while, the file disappears from the ls output. However, when we check the corresponding path in the bucket using MinIO's web service or the MinIO pod node, the newly created file is still present.
Additionally, we created other pods that use subPath to mount the same directory and scheduled them on the same Kubernetes node as the problematic pod. In the new pod, after creating new files, the files are visible both in the new pod and in MinIO, and the new pod can also see the files that were previously created in the problematic pod and later disappeared. However, these files remain invisible in the problematic pod.
On the host machine, we can see the relevant mount information using the mount -l command. The issue seems to be related to geesefs. We are looking for help from the community to resolve this issue.
We are using multiple pods to access the same PVC/PV with subPath mounting. During usage, we noticed that in one of the pods, after creating a new file in the subPath mount, the file is initially visible when using the ls command, but after a while, the file disappears from the ls output. However, when we check the corresponding path in the bucket using MinIO's web service or the MinIO pod node, the newly created file is still present.
Additionally, we created other pods that use subPath to mount the same directory and scheduled them on the same Kubernetes node as the problematic pod. In the new pod, after creating new files, the files are visible both in the new pod and in MinIO, and the new pod can also see the files that were previously created in the problematic pod and later disappeared. However, these files remain invisible in the problematic pod.
On the host machine, we can see the relevant mount information using the mount -l command. The issue seems to be related to geesefs. We are looking for help from the community to resolve this issue.