Confirmed - this was a bug on our side (fixed). We weren't checking that attachmentSet->status is 'attached' before initiating a volume mount on instance, only checked volume status to be "in-use".
On 8 дек, 11:59, Sam <[EMAIL PROTECTED]> wrote: > I have an EBS storage attached to my app instance. I have mkdir > fjstorage on application server and then created 2 symlinks to store > the local files on the server. Then I terminated and synchronised the > farm and restarted the farm. Everything worked fine. I stopped the > farm on friday and then restarted it today. > Everything else is fine on the app server but the /fjstorage directory > where EBS is to be mounted does not exist. > My settings for EBS in the app server role was to create 10GB storage > and attach it automatically to /fjstorage directory on the app server. > I had similar problem before which I was told that they had fixed it. > This is again happening. > Could you please help urgently as we are going to put an application > live this week and this sort of problem with EBS storage defnitely > won't help. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
