service instance for Dingo Postgresql is not getting created

[cfmagnum]

The service instance is getting stuck in 'create in progress' state
After checking the logs for cell vm we found that the store is getting full giving no space left error

[drnic]

Does the system recommence behaving ok if you expand your persistent disk?

Do you think the persistent volume was more full than you expected?

[cfmagnum]

After expanding disk size,got below error

[drnic]

Is this on bosh-lite (which can weird errors in general with /var/vcap/store during updates) or which CPI?

…

________________________________ From: cfmagnum <notifications@github.com> Sent: Tuesday, August 22, 2017 1:02:53 AM To: dingotiles/dingo-postgresql-release Cc: Dr Nic Williams; Comment Subject: Re: [dingotiles/dingo-postgresql-release] service instance for Dingo Postgresql is not getting created (#29) After expanding disk size,got below error [dingo_disk_increase]<https://user-images.githubusercontent.com/13657881/29525315-dc1dfe2e-86af-11e7-8a67-ff2afe53cfd9.png> — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#29 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AAAAbPAnC3rWqfafi3CBO6KPC3VxzbNBks5saZwdgaJpZM4O56qc>.

[cfmagnum]

This error is on BOSH and CPI is AWS.Can you suggest any resolution for this.

[cfmagnum]

Hi @drnic
On dingo-postgresql we have encoutered the issue of persistant disk full, while end users creating service instances.

I believe disk is getting full more than expected behaviour.

We had temporarily fixed the issue by unmounting the existing disk, redeploy then mount it back [EBS].

Did anyone faced this issue repeatedly and what would be the root cause for this ?

Any Solutions to avoid redeployment repeatedly ?