How to identify the New LUN assigned to redhat system ? If there is multiple devices or LUN already
I have requested for a new LUN assignation of 100GB on my RedHat system. But there is already many devices which have size with 100GB, so how to identify the new lun on the system with size of 100GB.
Thanks in advance. |
It should be the one without a UUID. The blkid utility will list known devices with their UUID - but an uninitialized lun will not have a UUID.
A bit tricky, but compare the first column of the blkid output and the last column of the contents of /proc/partitions. The /proc/partitions will list all devices and their size - as well as any partitions on those devices. The new one should be the entry in /proc/partitions that doesn't exist in blkid list. Now, this is assuming the device is known as after a reboot. It is possible to force a rescan of devices (https://blogs.it.ox.ac.uk/oxcloud/20...e-new-storage/), but that may depend on your controllers (works for SAS/SATA, but I don't know how fibre channel devices would go). |
Hi jpollard,
Thanks for your replay on the post. |
Welcome.
There are sometimes faster ways but they depend on knowing how the system is configured first. One is knowing if all devices are given partitions. Thus for sdx in /proc/partitions there will be an sdx<n> where n is the partition on device sdx. The new device will not be partitioned, so there will only be the sdx entry - unless someone already partitioned it... Even the method I gave first is vulnerable to that - the person creating the lun may have initialized it to verify it was working properly... And that might give it a UUID. |
|
Hi ardvark71,
Thanks for your suggestion. Really I was trying to change my user name but unable to change, so I have just sent you the mail please change my user name as soon as possible. |
Quote:
Quote:
Regards... |
All times are GMT -5. The time now is 06:09 AM. |