[Pls help me] PostgreSQL Disk Full - Service Down & Clone Stuck at 76%

Waiting for author response

Ppxw3504kDEVELOPER1d ago

My n8n service is currently unavailable because the PostgreSQL disk is 100% full, causing the container to enter a CrashLoopBackOff state.

Following the system prompt, I purchased a new server and attempted to "Clone" the project, but the process has been stuck at 76% (Volume Copy) for a long time.

Since I have critical production workflows in this instance, could you please:

Manually expand the disk size of my original PostgreSQL service so I can start it and clean up data?
Or, help fix the stuck cloning process so I can migrate to the new server immediately?

My original project ID: n8nwori.zeabur.app

1 Reply

BCBohan ChenEMPLOYEE18h ago

Hello, we are responding to the questions from both posts together:

Regarding PostgreSQL disk space: The disk issue on the shared cluster has been resolved, and your PostgreSQL service should now start normally. Please check the service status in the Dashboard.

Regarding the project clone getting stuck at 76%: The cloning failed because your new server, Tencent Ashburn 2C 2GB, only has 2GB of RAM, which is insufficient to complete the volume cloning operation. The cloning process requires enough memory as a buffer; the remaining memory on the 2GB machine is not enough, causing the task to abort.

If you still need to migrate the project to the new server, please go to Servers → Tencent Ashburn → Resize, upgrade to at least 4GB of RAM, and then re-trigger the clone. However, if the service on the shared cluster has returned to normal, you can also continue using the original deployment.

Please let us know if you have any further questions.

Add a Reply

Forum

1 Reply