We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
On an EC2 instance, disko identifies both SSD and HDD as SSD.
Here is an example, from a c1.medium:
Block device mappings are:
$ u=http://169.254.169.254/latest/meta-data/block-device-mapping/; $ for x in $(curl --silent $u); do echo $x=$(curl --silent $u/$x); done ami=/dev/sda1 ephemeral0=sdd root=/dev/sda1 swap=sdc $ ./demo/demo disk scan { "xvda": { "name": "xvda", "path": "/dev/xvda", "size": 8589934592, "sectorSize": 512, "type": "SSD", "attachment": "UNKNOWN", "partitions": { "1": { "start": 1048576, "last": 8589917695, "id": "00000000-0000-0000-0000-000000000000", "type": "00000000-0000-0000-0000-000000000083", "name": "", "number": 1 } }, "table": "MBR", "udevInfo": { "name": "xvda", "sysPath": "/devices/vbd-768/block/xvda", "symLinks": null, "properties": { "DEVNAME": "/dev/xvda", "DEVPATH": "/devices/vbd-768/block/xvda", "DEVTYPE": "disk", "ID_PART_TABLE_TYPE": "dos", "ID_PART_TABLE_UUID": "fe3a9f65", "MAJOR": "202", "MINOR": "0", "SUBSYSTEM": "block", "TAGS": ":systemd:", "USEC_INITIALIZED": "2944484" } } }, "xvdc": { "name": "xvdc", "path": "/dev/xvdc", "size": 939524096, "sectorSize": 512, "type": "SSD", "attachment": "UNKNOWN", "partitions": {}, "table": "NONE", "udevInfo": { "name": "xvdc", "sysPath": "/devices/vbd-51744/block/xvdc", "symLinks": [ "disk/by-uuid/3875a330-8e81-4db6-9319-7c1dbe5deff0" ], "properties": { "DEVLINKS": "/dev/disk/by-uuid/3875a330-8e81-4db6-9319-7c1dbe5deff0", "DEVNAME": "/dev/xvdc", "DEVPATH": "/devices/vbd-51744/block/xvdc", "DEVTYPE": "disk", "ID_FS_TYPE": "swap", "ID_FS_USAGE": "other", "ID_FS_UUID": "3875a330-8e81-4db6-9319-7c1dbe5deff0", "ID_FS_UUID_ENC": "3875a330-8e81-4db6-9319-7c1dbe5deff0", "ID_FS_VERSION": "1", "MAJOR": "202", "MINOR": "32", "SUBSYSTEM": "block", "TAGS": ":systemd:", "USEC_INITIALIZED": "3153128" } } }, "xvdd": { "name": "xvdd", "path": "/dev/xvdd", "size": 365041287168, "sectorSize": 512, "type": "SSD", "attachment": "UNKNOWN", "partitions": {}, "table": "NONE", "udevInfo": { "name": "xvdd", "sysPath": "/devices/vbd-51760/block/xvdd", "symLinks": [ "disk/by-uuid/8875aa95-01ad-4133-a2ae-237f49b13a8c" ], "properties": { "DEVLINKS": "/dev/disk/by-uuid/8875aa95-01ad-4133-a2ae-237f49b13a8c", "DEVNAME": "/dev/xvdd", "DEVPATH": "/devices/vbd-51760/block/xvdd", "DEVTYPE": "disk", "ID_FS_TYPE": "ext3", "ID_FS_USAGE": "filesystem", "ID_FS_UUID": "8875aa95-01ad-4133-a2ae-237f49b13a8c", "ID_FS_UUID_ENC": "8875aa95-01ad-4133-a2ae-237f49b13a8c", "ID_FS_VERSION": "1.0", "MAJOR": "202", "MINOR": "48", "SUBSYSTEM": "block", "TAGS": ":systemd:", "USEC_INITIALIZED": "2941507" } } }, "xvdf": { "name": "xvdf", "path": "/dev/xvdf", "size": 1073741824, "sectorSize": 512, "type": "SSD", "attachment": "UNKNOWN", "partitions": {}, "table": "NONE", "udevInfo": { "name": "xvdf", "sysPath": "/devices/vbd-51792/block/xvdf", "symLinks": null, "properties": { "DEVNAME": "/dev/xvdf", "DEVPATH": "/devices/vbd-51792/block/xvdf", "DEVTYPE": "disk", "MAJOR": "202", "MINOR": "80", "SUBSYSTEM": "block", "TAGS": ":systemd:", "USEC_INITIALIZED": "2085116822" } } } }
The text was updated successfully, but these errors were encountered:
I just put up #79 which will identify the xen blkfront devices as XENBUS attachment.
The SSD issue is tricky, as we determine if something is an SSD based on SysPath /queue/rotational and all EC2 devices list a 0 there.
Sorry, something went wrong.
No branches or pull requests
On an EC2 instance, disko identifies both SSD and HDD as SSD.
Here is an example, from a c1.medium:
Block device mappings are:
The text was updated successfully, but these errors were encountered: