Dear Kevin, We've spend few hours analyzing your logs and came to conclusion that you were detaching volumes that Scalr attaches for you automatically and attaching another one manually. Is this a right conclusion?
If you want some particular volume to be attached, just make a snapshot of it, and choose " Attach volume from snapshot:" on EBS tab. On 10.12.08 17:45, "Kevin Baker" <[EMAIL PROTECTED]> wrote: > > I will be retesting with a fresh image today, and will update this > thread. > > On Dec 10, 2008, at 1:21 AM, Sam <[EMAIL PROTECTED]> wrote: > >> >> This is worrying as my application heavily rely on the application to >> attach to the already existing EBS and if it attaches new EBS >> everytime my application will fail. >> Kevin, did you recently checked this after a few problems were fixed >> related to EBS? >> >> On Dec 9, 7:28 pm, Kevin Baker <[EMAIL PROTECTED]> wrote: >>> Alex, >>> >>> I have had an EBS instance attach successfully each time, however >>> it is >>> always a new EBS instance. >>> >>> It goes something like this: >>> >>> * Create EBS >>> * Format and attach to Instance >>> * restart instance >>> * new EBS is created >>> * Previous EBS is orphaned >>> >>> So each time I have an EBS, but just not the previous one. >>> >>> Alex Kovalyov wrote: >>>> We've checked your log and found all attach and mount attempts >>>> successful. >>>> Please provide more details. >>> >>>> On 8 дек, 22:55, Kevin Baker <[EMAIL PROTECTED]> wrote: >>> >>>>> So would this apply to any EBS that would have been attached on >>>>> startup? >>> >>>>> I have an EBS on my MySQL instance that has not been automatically >>>>> reattaching on restart. >>> >>>>> Alex Kovalyov wrote: >>> >>>>>> 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 scalr-discuss@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
