debug command fatal

[YunhuiChen]

What happened:
root@chaos-k8s-001:~/chenyunhui# ./juicefs/juicefs version
juicefs version 1.3.0-dev+2025-03-04.17484b49

mount :

root@chaos-k8s-001:~/chenyunhui# ps -ef|grep juicefs1
root      479628       1  0 Mar04 ?        00:00:11 ./juicefs mount redis://172.28.39.187:6379/1 /juicefs1 --cache-dir /data/cache-juicefs -d
root      479640  479628  5 Mar04 ?        00:52:55 /root/chenyunhui/juicefs/juicefs mount redis://172.28.39.187:6379/1 /juicefs1 --cache-dir /data/cache-juicefs -d
root      553550       1  0 Mar04 ?        00:00:08 ./juicefs mount redis://172.28.39.187:6379/1 /juicefs1 --cache-dir /data/cache-juicefs --enable-xattr -d

root@chaos-k8s-001:~/chenyunhui# ./juicefs/juicefs debug --out-dir=debug /juicefs1

Platform:
linux amd64

Kernel:
Linux version 5.4.0-77-generic (buildd@lgw01-amd64-028) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021

OS:
LSB Version:	core-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch
Distributor ID:	Ubuntu
Description:	Ubuntu 20.04.2 LTS
Release:	20.04
Codename:	focal

2025/03/05 10:31:30.793649 juicefs[1314624] <INFO>: mount point:/juicefs1 pid: uid: [debug@debug.go:601]
2025/03/05 10:31:30.793742 juicefs[1314624] <FATAL>: failed to get mount command: find more than one mount process for /juicefs1 [main@main.go:31]

What you expected to happen:

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

Anything else we need to know?

Environment:

• JuiceFS version (use juicefs --version) or Hadoop Java SDK version:
• Cloud provider or hardware configuration running JuiceFS:
• OS (e.g cat /etc/os-release):
• Kernel (e.g. uname -a):
• Object storage (cloud provider and region, or self maintained):
• Metadata engine info (version, cloud provider managed or self maintained):
• Network connectivity (JuiceFS to metadata engine, JuiceFS to object storage):
• Others: