we're going to be re-mounting ephemeral device to another mountpoint of your preference. next update will bring this up to scalr.net.
2009/6/4 Alex Kovalyov <[email protected]> > > Devices aligned per amazon's recommendations: > > http://docs.amazonwebservices.com/AWSEC2/latest/DeveloperGuide/index.html?instance-storage.html > > On 2 июн, 22:21, Niv <[email protected]> wrote: > > Hello. > > I've started a new MySQL EBS on the largest instance possible, and I > > have a problem. > > > > The EBS volume mounts to /mnt - replacing the ephemeral storage. Why > > is that? I need the additional drive! > > > > SCALR(instance-up.sh): Successfully attached 'vol-10ce2279' as '/dev/ > > sdo' on 'i-e5f1bf8c'. > > sdo: unknown partition table > > SCALR(instance-up.sh): MySQL EBS volume 'vol-10ce2279' has been > > successfully attached as '/dev/sdo'. > > kjournald starting. Commit interval 5 seconds > > EXT3 FS on sdo, internal journal > > EXT3-fs: mounted filesystem with ordered data mode. > > SCALR(instance-up.sh): MySQL EBS volume 'vol-10ce2279' has been > > successfully mounted to /mnt. [***] > > SCALR(mysql-init.sh): Not fetching MySQL data snapshot from S3 > > (because of EBS volume chosen as data storage). > > SCALR(mysql-init.sh): Locked MySQL data bundle creation (PID: 3227). > > SCALR(mysql-init.sh): Bundling MySQL data. > > > > 2. The > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
