Fatal error when mounting pvc

[xianml]

What happened:

failed mount error

 object=Pod/status-ci-iris-9fcac5-5fb9567765-qknr9 reason=FailedMount message=MountVolume.SetUp failed for volume "pvc-84a0b873-84f8-4f6f-8b3e-21c1ba85b4de" : rpc error: code = Internal desc = Could not mount juicefs: mount redis://:****@10.243.104.12:6379/1 at /jfs/pvc-84a0b873-84f8-4f6f-8b3e-21c1ba85b4de-mysipn failed, mountpod: juicefs-gke-bc-mt-guc1-bc-mt-guc1-main-pr80-s-f3339251-9r5m-pvc-84a0b873-84f8-4f6f-8b3e-21c1ba85b4de-cbrlzn, failed log:   "DirStats": true,
  "EnableACL": false
} [format.go:521]
2024/11/08 00:19:20.924926 juicefs[1] <INFO>: Meta address: redis://:****@10.243.104.12:6379/1 [interface.go:504]
2024/11/08 00:19:20.944786 juicefs[1] <WARNING>: AOF is not enabled, you may lose data if Redis is not shutdown properly. [info.go:84]
2024/11/08 00:19:20.944841 juicefs[1] <WARNING>: maxmemory_policy is "volatile-lru",  we will try to reconfigure it to 'noeviction'. [redis.go:3498]
2024/11/08 00:19:20.948748 juicefs[1] <ERROR>: try to reconfigure maxmemory-policy to 'noeviction' failed: ERR unknown command 'config', with args beginning with: 'set' 'maxmemory-policy' 'noeviction'  [redis.go:3500]
2024/11/08 00:19:20.952742 juicefs[1] <INFO>: Ping redis latency: 3.956079ms [redis.go:3515]
2024/11/08 00:19:20.965006 juicefs[1] <INFO>: Data use s3://bc-mt-guc1-infra/juicefs-prod/ [mount.go:629]
2024/11/08 00:19:21.797835 juicefs[22] <INFO>: Meta address: redis://:****@10.243.104.12:6379/1 [interface.go:504]
2024/11/08 00:19:21.817790 juicefs[22] <WARNING>: AOF is not enabled, you may lose data if Redis is not shutdown properly. [info.go:84]
2024/11/08 00:19:21.817864 juicefs[22] <WARNING>: maxmemory_policy is "volatile-lru",  we will try to reconfigure it to 'noeviction'. [redis.go:3498]
2024/11/08 00:19:21.821752 juicefs[22] <ERROR>: try to reconfigure maxmemory-policy to 'noeviction' failed: ERR unknown command 'config', with args beginning with: 'set' 'maxmemory-policy' 'noeviction'  [redis.go:3500]
2024/11/08 00:19:21.825752 juicefs[22] <INFO>: Ping redis latency: 3.943369ms [redis.go:3515]
2024/11/08 00:19:21.842041 juicefs[22] <INFO>: Data use s3://bc-mt-guc1-infra/juicefs-prod/ [mount.go:629]
2024/11/08 00:19:21.842080 juicefs[22] <INFO>: JuiceFS version 1.2.1+2024-08-30.cd871d19 [mount.go:659]
2024/11/08 00:19:21.843073 juicefs[22] <INFO>: Disk cache (/mnt/disks/raid/0/juicefs-cache/2a241832-574f-48d0-9a32-cf033a7fcfd5/): capacity (100 GiB), free ratio 10%!!(MISSING),(MISSING) used ratio - [space 3.1%!!(MISSING),(MISSING) inode 0.5%!!(MISSING)](MISSING), max pending pages 15 [disk_cache.go:144]
2024/11/08 00:19:21.868751 juicefs[22] <INFO>: Create session 55796 OK with version: 1.2.1+2024-08-30.cd871d19 [base.go:398]
....................
2024/11/08 00:19:31.012844 juicefs[1] <FATAL>: The mount point is not ready in 10 seconds, exit it [mount_unix.go:211]

What you expected to happen:

no error

How to reproduce it (as minimally and precisely as possible):

mount pod

Anything else we need to know?

Environment:
Helm Chart version: 0.21.1 (juicefs-csi-driver)

• JuiceFS version (use juicefs --version) or Hadoop Java SDK version: juicefs version 1.2.1+2024-08-30.cd871d19
• Cloud provider or hardware configuration running JuiceFS: gcp
• OS (e.g cat /etc/os-release): Debian GNU/Linux 10 (buster)
• Kernel (e.g. uname -a): Linux pvc-0702676d-debd-45f3-ba38-5b5d0ddbd0c7 6.1.100+ update reader length after write #1 SMP PREEMPT_DYNAMIC Sat Aug 10 14:21:56 UTC 2024 x86_64 GNU/Linux
• Object storage (cloud provider and region, or self maintained): cloud provider gcs
• Metadata engine info (version, cloud provider managed or self maintained): Redis
• Network connectivity (JuiceFS to metadata engine, JuiceFS to object storage):
• Others:

[xianml]

it still happened in the latest version. same error as #5060

[polyrabbit]

You may pick #5171, and it should print a stack trace to show where the mount process is stuck.

[xianml]

Great. I will try