Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

i created an amazon ec2 ubuntu m1.small instance and then created an ami to back it up, when i loaded that ami as a spot instance and booted it, it did not have any contents in /mnt parition.

So while creating ami backup why did it skip /mnt? is this /mnt part of EBS??

# /etc/fstab: static file system information.
# <file system>                                 <mount point>   <type>  <options>       <dump>  <pass>
proc                                            /proc           proc    nodev,noexec,nosuid 0       0
LABEL=uec-rootfs                                       /               ext4    defaults        0       0
/dev/xvda2      /mnt    auto    defaults,nobootwait,comment=cloudconfig 0      2
/dev/xvda3      none    swap    sw,comment=cloudconfig  0       0

since /mnt holds all my websites and mysql data, how can this be added to the ami instance?

share|improve this question

No, /mnt is the ephemeral data store that gets wiped on reboot. You really shouldn't store anything in there that you want to survive. Make your root partition bigger and put all your data in there, or create a separate EBS instance and mount it somewhere else.

share|improve this answer
what if i convert it to an EBS instance and then use /mnt within the EBS instance will that be OK? EBS should not delete the data right? – krisdigitx Aug 15 '11 at 8:29
Like I said, /mnt is the ephemeral data. You can create a separate EBS instance and put your data there. – womble Aug 15 '11 at 11:06

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.