{"id":768,"date":"2026-04-29T16:30:40","date_gmt":"2026-04-29T15:30:40","guid":{"rendered":"https:\/\/guillaumesblog.net\/?p=768"},"modified":"2026-04-29T16:49:35","modified_gmt":"2026-04-29T15:49:35","slug":"cross-identify-cloud-storage-with-instance-storage","status":"publish","type":"post","link":"https:\/\/guillaumesblog.net\/index.php\/cross-identify-cloud-storage-with-instance-storage\/","title":{"rendered":"Cross identify cloud storage with instance storage"},"content":{"rendered":"\n

The other day, as I was clearing out storage on a VM and consolidating logical volumes into a lesser number of physical volumes, I ran into an issue where there was no way for me to identify to which cloud block storage my freshly freed \/dev\/sdc disk did correspond to… So how was I supposed to know which block to delete in the console and save money?<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n\n\n\n\n

Turned out that I was using the ‘paravirtualisation’ option to attach the block device, and for that reason I was not able to establish a cross reference between the block volume and my VM device name. If you read this article and do know how to do it please let me know in the comments…<\/p>\n\n\n\n

Briefly before I carry on, in this article I discuss concepts belonging to the Linux Logical Volume Management (LVM). It is a more flexible approach to managing disk space as it allows for resizing partitions on the fly, creating snapshots, and combining multiple physical disks into one large virtual one. Please read here<\/a> if you are unfamiliar with it.<\/p>\n\n\n\n

Back to the issue now, and the solution I offer comes with the hidden benefit of a performance increase. If you want to delete storage resources without triggering yourself an anxiety panic, here is the way to do it:<\/p>\n\n\n\n

Mount block devices in ISCSI mode, they default to paravirtualised, change it like so<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

if you happen to use any supported cloud platform images here<\/a>, the cloud agent would do the ISCSI connection for you. This is not my case in this example as I am using RHEL 8 so let’s run the commands together.<\/p>\n\n\n\n

My VM shows two attached block volumes<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

but the command line only shows my boot volume.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Thankfully, the console offers the ISCSI commands to run, very handy!<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

but before being able to do that so need to verify you have the correct packages installed, this one in particular iscsi-initiator-utils<\/em><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Let’s give it a go then, copy paste commands from the console and stick it in your terminal<\/p>\n\n\n\n

sudo iscsiadm -m node -o new -T iqn.2015-12.com.oracleiaas:cf78e312-3a91-4a24-aa86-2ec0f5756dcd -p 169.254.2.6:3260\nsudo iscsiadm -m node -o update -T iqn.2015-12.com.oracleiaas:cf78e312-3a91-4a24-aa86-2ec0f5756dcd -n node.startup -v automatic\nsudo iscsiadm -m node -T iqn.2015-12.com.oracleiaas:cf78e312-3a91-4a24-aa86-2ec0f5756dcd -p 169.254.2.6:3260 -l<\/code><\/pre>\n\n\n\n
Block volumes are now available inside the VM! Ready to be partitioned and formatted \ud83d\ude42<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
Let’s identify the ids of these disks. There is a good guide here<\/a> about the available iscsi utilities. I run the command below I am now able to see which iqn belong to which device name.<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
and cross check in the cloud tenancy that sdc belongs to ‘block1’, in this instance.  Beware that the mapping between device name and block storage can change, in order to maintain consistency across reboots it is necessary to set up correctly the \/etc\/fstab file, please see here<\/a>.<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
See you!<\/p>\n\n\n\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
The other day, as I was clearing out storage on a VM and consolidating logical volumes into a lesser number of physical volumes, I ran into an issue where there was no way for me to identify to which cloud block storage my freshly freed \/dev\/sdc disk did correspond to… So how was I supposed … Continue reading “Cross identify cloud storage with instance storage”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-768","post","type-post","status-publish","format-standard","hentry","category-conversation"],"_links":{"self":[{"href":"https:\/\/guillaumesblog.net\/index.php\/wp-json\/wp\/v2\/posts\/768","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/guillaumesblog.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/guillaumesblog.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/guillaumesblog.net\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/guillaumesblog.net\/index.php\/wp-json\/wp\/v2\/comments?post=768"}],"version-history":[{"count":11,"href":"https:\/\/guillaumesblog.net\/index.php\/wp-json\/wp\/v2\/posts\/768\/revisions"}],"predecessor-version":[{"id":789,"href":"https:\/\/guillaumesblog.net\/index.php\/wp-json\/wp\/v2\/posts\/768\/revisions\/789"}],"wp:attachment":[{"href":"https:\/\/guillaumesblog.net\/index.php\/wp-json\/wp\/v2\/media?parent=768"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/guillaumesblog.net\/index.php\/wp-json\/wp\/v2\/categories?post=768"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/guillaumesblog.net\/index.php\/wp-json\/wp\/v2\/tags?post=768"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}