In this situation, a device that should be mounted on /data could end-up being mounted on /logs.
Linux mount use wipefs driver#
The block device driver can assign NVMe device names in a different order than what you specified for the volumes in the block device mapping. In this case, it will fail to mount.Īmazon EBS volumes are exposed as NVMe block devices on instances built on the AWS Nitro System. If you mount a device on T2 called /dev/sdc, when you change the instance family to T3 the same device won’t be called /dev/sdc anymore. T2 uses /dev/sd, while T3 uses /dev/nvmen1. The device name can be different between instance families, such as T2 and T3. The customer wants to avoid the situation where a volume is mounted on a different mount point just because the device name changed, or the device name doesn’t exist because the name pattern changed.Ĭustomers who want to utilize the latest instance family usually change the instance type when a new one is available. As the device name can change, the customer shouldn’t rely on the device name to mount volumes from it. In this case, device name can vary depending on some facts, such as virtualization type, instance type, or operating system. This post is written by: Leonardo Azize Martins, Cloud Infrastructure Architect, Professional ServicesĬustomers often use Amazon Elastic Compute Cloud (Amazon EC2) Linux based instances with many Amazon Elastic Block Store (Amazon EBS) volumes attached.
0 kommentar(er)
