EC2：EBS设备ID的困惑（的/ dev / SDF与为/ dev / xvdf） [英] EC2: EBS device id confusion (/dev/sdf vs. /dev/xvdf)

问题描述

我附上EBS卷到我的EC2实例，把它变成一个EXT3文件系统，并成功地安装它。不过，我一下失去一点点最初主要是由于什么AWS控制台说我的EBS设备ID了。

I attached an EBS volume to my EC2 instance, turned it into a EXT3 file system, and successfully mounted it. However, I was thrown off a little bit initially mainly due to what the AWS console said my EBS device ID was.

按照AWS控制台：

i-xxxxxxx :/dev/sdf (attached)

我把这个的意思是我的连接EBS设备ID是的/ dev / SDF。所以，当我试图打开设备到文件系统中使用此设备ID，我收到以下错误消息。

I took this to mean that my attached EBS device id was /dev/sdf. So when I attempted to turn the device into a file system using this device id, I received the following error message.

ubuntu@ip-xx-xx-xx-xx:~$ mkfs -t ext3 /dev/sdf
mke2fs 1.42 (29-Nov-2011)
Could not stat /dev/sdf --- No such file or directory
The device apparently does not exist; did you specify it correctly?

然后研究一点点后，我发现这的文章，并随后发现了通过运行猫的/ proc /分区，我的真正的设备ID是的/ dev / xvdf不是/ dev / SDF。

Then after researching a little bit, I found this article and then subsequently found out by running cat /proc/partitions that my true device id was /dev/xvdf not /dev/sdf.

我的问题是，为什么是AWS控制台说这是为/ dev / SDF时，它实际上为/ dev / xvdf？我认为必须有某种这合乎逻辑的解释。

My question is why is the AWS console saying it's /dev/sdf when it's actually /dev/xvdf? I think there has to be some kind of logical explanation for this.

推荐答案

AWS连接通过的 AWS管理控制台：

注：新的Linux内核可以通过重命名你的设备到/ dev / xvdf   为/ dev / xvdp内部，即使在设备名称此处输入（和   在细节中所示）是/ dev / SDF通过的/ dev / SDP。

Note: Newer linux kernels may rename your devices to /dev/xvdf through /dev/xvdp internally, even when the device name entered here (and shown in the details) is /dev/sdf through /dev/sdp.

我没有这个信息，方便任何上游来源，但周杰伦朗姆酒的答案（不再相关）临时问题的 EBS磁盘作为启动设备/ dev / xvde，但映射为/ dev / sda的属性此功能的 Xen的blkfront 驱动程序：

I don't have any upstream source for this information handy, but Jay Rum's answer to the (not longer relevant) temporary problem EBS Disks starting as device /dev/xvde, but mapped as /dev/sda attributes this functionality to the xen-blkfront driver:

的Xen的blkfront驱动程序，它允许虚拟机（即   EC2实例）访问底层块设备，传统   映射SDA，SDB ......到xvda，xvdb ... [...]

The "xen-blkfront" driver, which allows the virtual machines (i.e. the EC2 instances) to access the underlying block devices, traditionally mapped sda, sdb... to xvda, xvdb..., [...]

最后，cyberx86答案如何访问提供了详细的说明和解释，在Amazon EC2上的附着量该设备命名不匹配，以及如何处理它，即确定目前可用的设备等。

Finally, cyberx86' answer to How do I access the attached volume in Amazon EC2 provides a detailed and illustrated explanation of this device naming mismatch and how to deal with it, i.e. identify the currently available devices etc.

<子>注：这个问题已经回答了在8月24日'12，但与6 upvotes这个答案得到了5月1日'13删除了的社区版主的（即RESP自动化。处理）的非透明的理由（显然是因为的用户被删除的） - 反正，我已经加回到原来的内容略有变化，从我的角度来看

_{Note: This question had already been answered in Aug 24 '12, but that answer with 6 upvotes got deleted in May 01 '13 by the Community Moderator (i.e. a resp. automation process) for non transparent reasons (apparently because the User was removed) - anyway, I've added back a slight variation of the original content from my point of view.}

这篇关于EC2：EBS设备ID的困惑（的/ dev / SDF与为/ dev / xvdf）的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！