On Fri, 3 Apr 2020, at 22:56, Noah Meyerhans wrote:
> On Fri, Apr 03, 2020 at 06:16:33PM +0200, Jonathan Ballet wrote:
> > In its own Linux image, AWS apparently ships a set of udev rules + a
> > script to get these device names out of the information exposed by the
> > NVMe devices, which create
On Fri, Apr 03, 2020 at 06:16:33PM +0200, Jonathan Ballet wrote:
> On AWS Nitro instances, EBS volumes are exposed as NVMe block devices by
> the kernel on the /dev/nvme* paths.
>
> The AWS documentation "Identifying the EBS Device" says that the Linux
> kernel doesn't guarantee the creation
On 2020-04-03 18:16:33, Jonathan Ballet wrote:
> Hi,
>
> On AWS Nitro instances, EBS volumes are exposed as NVMe block devices by
> the kernel on the /dev/nvme* paths.
>
> The AWS documentation "Identifying the EBS Device" says that the Linux
> kernel doesn't guarantee the creation order of
Hi,
On AWS Nitro instances, EBS volumes are exposed as NVMe block devices by
the kernel on the /dev/nvme* paths.
The AWS documentation "Identifying the EBS Device" says that the Linux
kernel doesn't guarantee the creation order of these devices, as they
are discovered in the order the devices
