E2 Instance With Local Storage?

0

Hi,

I browsed through types of instances and I noticed that c3.large has a SSD instead of EBS. Hence, I believe the instance has a local drive attached. And then I configured the "Instance store volumes" in EC2>Instances>Launch an instance: device name=/dev/sdb for volume 2 and /dev/sdc for volume 2. However, after I launched the instance and I didn't see /dev/sdb and /dev/sdc: $ ll /dev/ total 0 crw-r--r--. 1 root root 10, 235 Apr 28 12:18 autofs drwxr-xr-x. 2 root root 180 Apr 28 12:18 block drwxr-xr-x. 2 root root 2400 Apr 28 12:18 char crw--w----. 1 root tty 5, 1 Apr 28 12:19 console lrwxrwxrwx. 1 root root 11 Apr 28 12:18 core -> /proc/kcore drwxr-xr-x. 4 root root 80 Apr 28 12:18 cpu crw-------. 1 root root 10, 123 Apr 28 12:18 cpu_dma_latency drwxr-xr-x. 6 root root 120 Apr 28 12:18 disk drwxr-xr-x. 2 root root 60 Apr 28 12:18 dma_heap drwxr-xr-x. 3 root root 80 Apr 28 12:18 dri crw-rw----. 1 root video 29, 0 Apr 28 12:18 fb0 lrwxrwxrwx. 1 root root 13 Apr 28 12:18 fd -> /proc/self/fd crw-rw-rw-. 1 root root 1, 7 Apr 28 12:18 full crw-rw-rw-. 1 root root 10, 229 Apr 28 12:18 fuse crw-------. 1 root root 10, 228 Apr 28 12:18 hpet drwxr-xr-x. 2 root root 0 Apr 28 12:18 hugepages crw-------. 1 root root 10, 183 Apr 28 12:18 hwrng lrwxrwxrwx. 1 root root 12 Apr 28 12:18 initctl -> /run/initctl drwxr-xr-x. 3 root root 200 Apr 28 12:18 input crw-r--r--. 1 root root 1, 11 Apr 28 12:18 kmsg lrwxrwxrwx. 1 root root 28 Apr 28 12:18 log -> /run/systemd/journal/dev-log crw-rw----. 1 root disk 10, 237 Apr 28 12:18 loop-control drwxr-xr-x. 2 root root 60 Apr 28 12:18 mapper crw-------. 1 root root 10, 227 Apr 28 12:18 mcelog crw-r-----. 1 root kmem 1, 1 Apr 28 12:18 mem drwxrwxrwt. 2 root root 40 Apr 28 12:18 mqueue drwxr-xr-x. 2 root root 60 Apr 28 12:18 net crw-rw-rw-. 1 root root 1, 3 Apr 28 12:18 null crw-------. 1 root root 10, 144 Apr 28 12:18 nvram crw-r-----. 1 root kmem 1, 4 Apr 28 12:18 port crw-------. 1 root root 108, 0 Apr 28 12:18 ppp crw-rw-rw-. 1 root tty 5, 2 Apr 28 12:26 ptmx drwxr-xr-x. 2 root root 0 Apr 28 12:18 pts crw-rw-rw-. 1 root root 1, 8 Apr 28 12:18 random crw-rw-r--. 1 root root 10, 242 Apr 28 12:18 rfkill lrwxrwxrwx. 1 root root 4 Apr 28 12:18 rtc -> rtc0 crw-------. 1 root root 250, 0 Apr 28 12:18 rtc0 drwxrwxrwt. 2 root root 40 Apr 28 12:18 shm crw-------. 1 root root 10, 231 Apr 28 12:18 snapshot drwxr-xr-x. 2 root root 80 Apr 28 12:18 snd lrwxrwxrwx. 1 root root 15 Apr 28 12:18 stderr -> /proc/self/fd/2 lrwxrwxrwx. 1 root root 15 Apr 28 12:18 stdin -> /proc/self/fd/0 lrwxrwxrwx. 1 root root 15 Apr 28 12:18 stdout -> /proc/self/fd/1 crw-rw-rw-. 1 root tty 5, 0 Apr 28 12:18 tty crw--w----. 1 root tty 4, 0 Apr 28 12:18 tty0 crw--w----. 1 root tty 4, 1 Apr 28 12:19 tty1 crw--w----. 1 root tty 4, 10 Apr 28 12:18 tty10 crw--w----. 1 root tty 4, 11 Apr 28 12:18 tty11 crw--w----. 1 root tty 4, 12 Apr 28 12:18 tty12 crw--w----. 1 root tty 4, 13 Apr 28 12:18 tty13 crw--w----. 1 root tty 4, 14 Apr 28 12:18 tty14 crw--w----. 1 root tty 4, 15 Apr 28 12:18 tty15 crw--w----. 1 root tty 4, 16 Apr 28 12:18 tty16 crw--w----. 1 root tty 4, 17 Apr 28 12:18 tty17 crw--w----. 1 root tty 4, 18 Apr 28 12:18 tty18 crw--w----. 1 root tty 4, 19 Apr 28 12:18 tty19 crw--w----. 1 root tty 4, 2 Apr 28 12:18 tty2 crw--w----. 1 root tty 4, 20 Apr 28 12:18 tty20 crw--w----. 1 root tty 4, 21 Apr 28 12:18 tty21 crw--w----. 1 root tty 4, 22 Apr 28 12:18 tty22 crw--w----. 1 root tty 4, 23 Apr 28 12:18 tty23 crw--w----. 1 root tty 4, 24 Apr 28 12:18 tty24 crw--w----. 1 root tty 4, 25 Apr 28 12:18 tty25 crw--w----. 1 root tty 4, 26 Apr 28 12:18 tty26 crw--w----. 1 root tty 4, 27 Apr 28 12:18 tty27 crw--w----. 1 root tty 4, 28 Apr 28 12:18 tty28 crw--w----. 1 root tty 4, 29 Apr 28 12:18 tty29 crw--w----. 1 root tty 4, 3 Apr 28 12:18 tty3 crw--w----. 1 root tty 4, 30 Apr 28 12:18 tty30 crw--w----. 1 root tty 4, 31 Apr 28 12:18 tty31 crw--w----. 1 root tty 4, 32 Apr 28 12:18 tty32 crw--w----. 1 root tty 4, 33 Apr 28 12:18 tty33 crw--w----. 1 root tty 4, 34 Apr 28 12:18 tty34 crw--w----. 1 root tty 4, 35 Apr 28 12:18 tty35 crw--w----. 1 root tty 4, 36 Apr 28 12:18 tty36 crw--w----. 1 root tty 4, 37 Apr 28 12:18 tty37 crw--w----. 1 root tty 4, 38 Apr 28 12:18 tty38 crw--w----. 1 root tty 4, 39 Apr 28 12:18 tty39 crw--w----. 1 root tty 4, 4 Apr 28 12:18 tty4 crw--w----. 1 root tty 4, 40 Apr 28 12:18 tty40 crw--w----. 1 root tty 4, 41 Apr 28 12:18 tty41 crw--w----. 1 root tty 4, 42 Apr 28 12:18 tty42 crw--w----. 1 root tty 4, 43 Apr 28 12:18 tty43 crw--w----. 1 root tty 4, 44 Apr 28 12:18 tty44 crw--w----. 1 root tty 4, 45 Apr 28 12:18 tty45 crw--w----. 1 root tty 4, 46 Apr 28 12:18 tty46 crw--w----. 1 root tty 4, 47 Apr 28 12:18 tty47 crw--w----. 1 root tty 4, 48 Apr 28 12:18 tty48 crw--w----. 1 root tty 4, 49 Apr 28 12:18 tty49 crw--w----. 1 root tty 4, 5 Apr 28 12:18 tty5 crw--w----. 1 root tty 4, 50 Apr 28 12:18 tty50 crw--w----. 1 root tty 4, 51 Apr 28 12:18 tty51 crw--w----. 1 root tty 4, 52 Apr 28 12:18 tty52 crw--w----. 1 root tty 4, 53 Apr 28 12:18 tty53 crw--w----. 1 root tty 4, 54 Apr 28 12:18 tty54 crw--w----. 1 root tty 4, 55 Apr 28 12:18 tty55 crw--w----. 1 root tty 4, 56 Apr 28 12:18 tty56 crw--w----. 1 root tty 4, 57 Apr 28 12:18 tty57 crw--w----. 1 root tty 4, 58 Apr 28 12:18 tty58 crw--w----. 1 root tty 4, 59 Apr 28 12:18 tty59 crw--w----. 1 root tty 4, 6 Apr 28 12:18 tty6 crw--w----. 1 root tty 4, 60 Apr 28 12:18 tty60 crw--w----. 1 root tty 4, 61 Apr 28 12:18 tty61 crw--w----. 1 root tty 4, 62 Apr 28 12:18 tty62 crw--w----. 1 root tty 4, 63 Apr 28 12:18 tty63 crw--w----. 1 root tty 4, 7 Apr 28 12:18 tty7 crw--w----. 1 root tty 4, 8 Apr 28 12:18 tty8 crw--w----. 1 root tty 4, 9 Apr 28 12:18 tty9 crw-rw----. 1 root dialout 4, 64 Apr 28 12:19 ttyS0 crw-rw----. 1 root dialout 4, 65 Apr 28 12:18 ttyS1 crw-rw----. 1 root dialout 4, 66 Apr 28 12:18 ttyS2 crw-rw----. 1 root dialout 4, 67 Apr 28 12:18 ttyS3 crw-rw----. 1 root kvm 10, 124 Apr 28 12:18 udmabuf crw-------. 1 root root 10, 239 Apr 28 12:18 uhid crw-------. 1 root root 10, 223 Apr 28 12:18 uinput crw-rw-rw-. 1 root root 1, 9 Apr 28 12:18 urandom crw-------. 1 root root 244, 0 Apr 28 12:18 usbmon0 crw-------. 1 root root 10, 126 Apr 28 12:18 userfaultfd crw-rw----. 1 root tty 7, 0 Apr 28 12:18 vcs crw-rw----. 1 root tty 7, 1 Apr 28 12:18 vcs1 crw-rw----. 1 root tty 7, 6 Apr 28 12:18 vcs6 crw-rw----. 1 root tty 7, 128 Apr 28 12:18 vcsa crw-rw----. 1 root tty 7, 129 Apr 28 12:18 vcsa1 crw-rw----. 1 root tty 7, 134 Apr 28 12:18 vcsa6 crw-rw----. 1 root tty 7, 64 Apr 28 12:18 vcsu crw-rw----. 1 root tty 7, 65 Apr 28 12:18 vcsu1 crw-rw----. 1 root tty 7, 70 Apr 28 12:18 vcsu6 drwxr-xr-x. 2 root root 60 Apr 28 12:18 vfio crw-------. 1 root root 10, 127 Apr 28 12:18 vga_arbiter crw-------. 1 root root 10, 137 Apr 28 12:18 vhci crw-rw-rw-. 1 root kvm 10, 238 Apr 28 12:18 vhost-net crw-rw-rw-. 1 root kvm 10, 241 Apr 28 12:18 vhost-vsock drwxr-xr-x. 2 root root 60 Apr 28 12:18 xen brw-rw----. 1 root disk 202, 0 Apr 28 12:18 xvda brw-rw----. 1 root disk 202, 1 Apr 28 12:18 xvda1 brw-rw----. 1 root disk 202, 2 Apr 28 12:18 xvda2 brw-rw----. 1 root disk 202, 3 Apr 28 12:18 xvda3 brw-rw----. 1 root disk 202, 4 Apr 28 12:18 xvda4 brw-rw----. 1 root disk 202, 16 Apr 28 12:18 xvdb brw-rw----. 1 root disk 202, 32 Apr 28 12:18 xvdc crw-rw-rw-. 1 root root 1, 5 Apr 28 12:18 zero

Why?

已提问 1 个月前19 查看次数
1 回答
0

The reason you're not seeing /dev/sdb and /dev/sdc is because EC2 instances with instance store volumes typically use different device names than what you specified. In your case, the instance store volumes are likely appearing as /dev/xvdb and /dev/xvdc.

From the output you provided, we can see that these devices are indeed present:

brw-rw----. 1 root disk 202, 16 Apr 28 12:18 xvdb brw-rw----. 1 root disk 202, 32 Apr 28 12:18 xvdc

These xvdb and xvdc devices correspond to the instance store volumes you configured. The "xv" prefix stands for "Xen virtual," which is the virtualization technology used by some EC2 instance types.

It's important to note that the device names you specify when launching an instance (like /dev/sdb and /dev/sdc) are often mapped to different device names within the instance's operating system. This mapping can vary depending on the instance type, virtualization method, and the AMI used.

To use these instance store volumes, you would need to mount them just as you would any other block device. Keep in mind that instance store volumes are ephemeral, meaning the data on them persists only for the life of the associated EC2 instance. If the instance stops, terminates, or fails, the data on instance store volumes is lost.
Sources
Amazon EBS volumes - Amazon EBS
Community | Connect to an Amazon EC2 Mac instance

profile picture
已回答 1 个月前

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈,并能促进提问者的职业发展。

回答问题的准则