-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
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
Formatting keep stuck at pulling image #282
Comments
Please follow the [Instructions for Asking Questions] (#271) You can modify the logging level like this: # ~/.curveadm/curveadm.cfg
[defaults]
log_level = info <---
… Then post your log (~/.curveadm/logs/xxx.log). |
Log:
Docker:
|
OS Kernel: 4.19.91 |
@mrdrivingduck Please be careful to hide your sensitive information (ip) and the like. |
@mrdrivingduck agjust the debug mode and retry. |
@Cyber-SiKu Thanks for your advice, I have wiped out the information. @caoxianfei1 Here is the result. Seems there are fewer lines? 🤔
|
I downgrade Docker and manually pull the image, and the format command proceeds and returns. Now it seems to be stuck at mounting:
Strange. There seems no Docker container running. |
|
Yes. Strange. Maybe the container quickly error out? #docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES |
I encountered the same problem. |
@mrdrivingduck It seems that format progress is not running because the format container exit because some exception,so the docker ps command not show the format container details and format device usage is 0 that show |
@caoxianfei1 Yes, I guess so. Any idea of why format container meets exception? |
|
@caoxianfei1 Seems the error comes from $ docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
d3f25d149c9c opencurvedocker/curvebs:v1.2 "/bin/bash /curveb..." 10 seconds ago Exited (0) 9 seconds ago curvebs-format-5382e6eb967461d786f8744b3104e9b7
4bf5f2e20c28 opencurvedocker/curvebs:v1.2 "/bin/bash /curveb..." 13 seconds ago Exited (0) 11 seconds ago curvebs-format-9e939ab24ceaaf69708ec2fb956ba69d
d0dfdd9d006e opencurvedocker/curvebs:v1.2 "/bin/bash /curveb..." 13 seconds ago Exited (0) 11 seconds ago curvebs-format-f41da9000e5270a4930662b848d85aaa $ docker logs d3f25d149c9c
E 2023-09-07T09:43:55.473361+0800 8 curve_format_main.cpp:215] disk free space not enough. $ cat format.yaml
container_image: opencurvedocker/curvebs:v1.2
host:
- server-host1
- server-host2
- server-host3
disk:
- /dev/osa:/data/chunkserver0:90 # device:mount_path:format_percent
- /dev/osb:/data/chunkserver1:90
- /dev/osc:/data/chunkserver2:90
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
ose 252:256 0 3.5T 0 disk
osc 252:128 0 3.5T 0 disk
osa 252:0 0 3.5T 0 disk
osf 252:320 0 3.5T 0 disk
osd 252:192 0 3.5T 0 disk
osb 252:64 0 3.5T 0 disk |
@mrdrivingduck It may be the percent is too big, set to 80 and retry again. we are looking into the specific reason |
Close it because too long time repose. you can open it again if occur. |
I'm trying to format my disks, but the progress seems not to move on. I'm using curveadm v0.3.0.
#curveadm format --status Get Format Status: [OK] Host Device MountPoint Formatted Status ---- ------ ---------- --------- ------ server-host1 /dev/osa /data/chunkserver0 1/90 Pulling image server-host1 /dev/osb /data/chunkserver1 1/90 Pulling image server-host1 /dev/osc /data/chunkserver2 1/90 Pulling image server-host2 /dev/osa /data/chunkserver0 1/90 Pulling image server-host2 /dev/osb /data/chunkserver1 1/90 Pulling image server-host2 /dev/osc /data/chunkserver2 1/90 Pulling image server-host3 /dev/osa /data/chunkserver0 1/90 Pulling image server-host3 /dev/osb /data/chunkserver1 1/90 Pulling image server-host3 /dev/osc /data/chunkserver2 1/90 Pulling image
If there any way to rollback this status and format again? I'm sure there is no image on my machine now:
The text was updated successfully, but these errors were encountered: