search

juicedata / juicefs

JuiceFS is a distributed POSIX file system built on top of Redis and S3.
https://juicefs.com
Apache License 2.0
10.9k stars 964 forks source link

The mount point is NOT ready in 10 seconds #4341

Open fourquadrantlogger opened 10 months ago

fourquadrantlogger commented 10 months ago

sudo juicefs mount redis://:123@192.168.1.19:30079/0 ~/myjfs 2024/01/15 10:12:25.860287 juicefs[58135] : Meta address: redis://:****@192.168.1.19:30079/0 [interface.go:497] 2024/01/15 10:12:26.011329 juicefs[58135] : AOF is not enabled, you may lose data if Redis is not shutdown properly. [info.go:84] 2024/01/15 10:12:26.050482 juicefs[58135] : Ping redis latency: 39.034541ms [redis.go:3593] 2024/01/15 10:12:26.091957 juicefs[58135] : Data use minio://192.168.1.17:9000/my-bucket-name/myjfs/ [mount.go:605] 2024/01/15 10:12:26.092206 juicefs[58135] : Disk cache (/Users/lipeng/.juicefs/cache/cc96db7d-f4ea-4112-9f69-a93dee4067ba/): capacity (102400 MB), free ratio (10%), max pending pages (15) [disk_cache.go:114] 2024/01/15 10:12:26.276698 juicefs[58135] : Create session 4 OK with version: 1.1.1+2023-11-28.437f4e6 [base.go:492] 2024/01/15 10:12:26.314174 juicefs[58135] : Prometheus metrics listening on 127.0.0.1:9567 [mount.go:160] 2024/01/15 10:12:26.314299 juicefs[58135] : Mounting volume myjfs at /Users/lipeng/myjfs ... [mount_unix.go:269] .................... 2024/01/15 10:12:36.101445 juicefs[58135] : The mount point is not ready in 10 seconds, exit it [mount_unix.go:59] lipeng@lipengdeMacBook-Pro ~ %

SandyXSD commented 10 months ago

Please try:

  1. make sure the mount point is accessible: ls ~/myjfs returns normally
  2. re-run the mount command with --debug
xfye commented 2 months ago

The same issue:

2024/09/11 16:03:13.293678 juicefs[3620] <DEBUG>: maxprocs: Leaving GOMAXPROCS=8: CPU quota undefined [maxprocs.go:47]
2024/09/11 16:03:13.293814 juicefs[3620] <INFO>: Meta address: postgres://postgres:****@127.0.0.1:5432/juicefs [interface.go:497]
[xorm] [info]  2024/09/11 16:03:13.293940 PING DATABASE pgx
2024/09/11 16:03:13.401267 juicefs[3620] <DEBUG>: Creating minio storage at endpoint http://192.168.2.10:9000/juicefs [object_storage.go:171]
2024/09/11 16:03:13.401362 juicefs[3620] <INFO>: Data use minio://192.168.2.10:9000/juicefs/myjfs/ [mount.go:605]
2024/09/11 16:03:13.401566 juicefs[3620] <INFO>: Disk cache (/var/jfsCache/7d4a2fde-d478-4f76-af85-0a8f819bc4d1/): capacity (102400 MB), free ratio (10%), max pending pages (51) [disk_cache.go:114]
2024/09/11 16:03:13.401636 juicefs[3620] <DEBUG>: Scan /var/jfsCache/7d4a2fde-d478-4f76-af85-0a8f819bc4d1/rawstaging to find staging blocks [disk_cache.go:619]
2024/09/11 16:03:13.401626 juicefs[3620] <DEBUG>: Scan /var/jfsCache/7d4a2fde-d478-4f76-af85-0a8f819bc4d1/raw to find cached blocks [disk_cache.go:572]
2024/09/11 16:03:13.401687 juicefs[3620] <DEBUG>: Found 0 cached blocks (0 bytes) in /var/jfsCache/7d4a2fde-d478-4f76-af85-0a8f819bc4d1/ with 77.672µs [disk_cache.go:604]
....................
2024/09/11 16:03:23.418912 juicefs[3620] <FATAL>: The mount point is not ready in 10 seconds, exit it [mount_unix.go:59]
xfye commented 2 months ago

In my case, pg standby server is not running and any write operation to master pg is blocked. After bring the pg standby server back, juicefs can mount successfully.