We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mount pod seems to umount its own mount point, causing app pod to lost connection
2024/04/25 03:38:48.316696 juicefs[64] <INFO>: mountpoint /jfs/juicefs-pv-utpxzh is broken: stat /jfs/juicefs-pv-utpxzh: transport endpoint is not connected, umount it [mount.go:140] 2024/04/25 03:38:48.690241 juicefs[157] <INFO>: JuiceFS version 5.0.10 (2024-01-31 10fbc97) [mount.go:632] 2024/04/25 03:38:48.697953 juicefs[157] <INFO>: Cache: /juicefs/cache/xx capacity: 1636000 MB [disk_cache.go:1074] 2024/04/25 03:38:48.698587 juicefs[157] <INFO>: Peer listen at 172.31.0.96:36639 [peer.go:1011] 2024/04/25 03:38:48.699661 juicefs[157] <INFO>: Mounting volume xx at /jfs/juicefs-pv-utpxzh ... [mount_unix.go:640] OK, liblib is ready at /jfs/juicefs-pv-utpxzh. 2024/04/25 03:38:53.422126 juicefs[64] <INFO>: watching /jfs/juicefs-pv-utpxzh, pid 157 [mount_unix.go:112]
The text was updated successfully, but these errors were encountered:
zxh326
No branches or pull requests
mount pod seems to umount its own mount point, causing app pod to lost connection
The text was updated successfully, but these errors were encountered: