a month ago
PROBLEMA: Volume MongoDB non viene riconosciuto dopo aumento di dimensione
SERVIZIO: MongoDB (ID: c7f3f6ec-618e-4ce1-8228-3601fa8cc188)
VOLUME: mongodb-volume (ID: ed5a5b9d-0471-4af0-a1c3-c67fe82244f3)
AMBIENTE: production
SITUAZIONE ATTUALE:
- Volume configurato a: 500 MB
- Spazio disponibile: ~229 MB
- Dati: 2860 eventi MongoDB
TENTATIVI FALLITI:
-
Aumento volume a 2GB → Deploy → Restart MongoDB → FALLITO
- MongoDB continua a riportare ~229 MB disponibili
- Warning: "available disk space of 229502976 bytes is less than required minimum of 524288000"
-
Aumento volume a 2GB → Deploy → Restart gregarious-presence → FALLITO
- Stesso warning persiste
-
Deploy forzato di MongoDB → FALLITO
- Volume ancora non riconosciuto
-
Eliminazione volume vecchio + Creazione nuovo volume 2GB → Deploy → FALLITO
- MongoDB ha due volumi montati sullo stesso path /data/db
- Conflitto di mount
-
Eliminazione volume vecchio → Deploy → FALLITO
- Volume vecchio ancora presente
IPOTESI:
- Il volume potrebbe non essere rimontato correttamente dopo l'aumento
- Potrebbe essere un bug di Railway con il mount dei volumi persistenti
- Il container MongoDB potrebbe non riconoscere il cambio di dimensione
RICHIESTA:
- Verificare se c'è un problema noto con il mount dei volumi
- Suggerire una soluzione per applicare l'aumento di volume
3 Replies
a month ago
Apologies, we only correspond in English. Please open a new thread in English.
Status changed to Closed Railway • about 1 month ago
Status changed to Solved Railway • about 1 month ago
Railway
Apologies, we only correspond in English. Please open a new thread in English.
a month ago
TITLE: MongoDB Volume Not Recognized After Size Increase
DESCRIPTION:
Hi Railway Team,
I'm experiencing a persistent issue with mounting a MongoDB volume.
Despite multiple attempts to increase the volume size, MongoDB continues
to not recognize the change.
TECHNICAL DETAILS:
Project: gregarious-presence (ID: 62182172-0449-4419-8216-dcc5b8636bd6)
Environment: production
Service: MongoDB (ID: c7f3f6ec-618e-4ce1-8228-3601fa8cc188)
Volume: mongodb-volume (ID: ed5a5b9d-0471-4af0-a1c3-c67fe82244f3)
CURRENT SITUATION:
- Volume configured to: 500 MB
- Available space: ~229 MB
- Critical data: 2860 MongoDB events
- Dependent application: gregarious-presence (FastAPI + MongoDB)
FAILED ATTEMPTS (5+ deployments):
-
Increase volume to 2GB → Deploy MongoDB → Restart MongoDB
Result: FAILED - MongoDB continues to report ~229 MB available
-
Increase volume to 2GB → Deploy MongoDB → Restart gregarious-presence
Result: FAILED - Warning persists
-
Forced MongoDB deployment after volume increase
Result: FAILED - Volume still not recognized
-
Delete old volume + Create new 2GB volume → Deploy
Result: FAILED - MongoDB has two volumes mounted on the same path /data/db
-
Delete old volume → Deploy
Result: FAILED - Old volume still present
ERROR IN LOGS:
HYPOTHESIS:
- The volume may not be remounted correctly after the increase
- Could be a bug in Railway's volume mounting system
- The MongoDB container may not recognize the size change
REQUEST:
- Verify if there is a known issue with volume mounting
- Suggest a solution to apply the volume increase
- Verify if the volume is correctly mounted in the container
Thank you for your help!
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Apologies, we only correspond in English. Please open a new thread in English.
Status changed to Closed Railway • about 1 month ago