What to do when partprobe doesn't detect new partition created?

Latest response

So I'm using gdisk to create a new partition to allocate towards LVM here at work and I'm having an issue with it.

At home, I have some instances of RHEL systems via AWS, and if I create say 100 to 125 MB partitions via gdisk. Once I create the new partition successfully, I can run partprobe, then blkid and see the UUID's tied to the partition. No need for a reboot.

At work, I just added 25 GB to a /var partition, however after running partprobe and blkid, I never saw the UUID, however I could see the new partition via gdisk.

So, in order to see the new partition, I reboot the vm and then I was able to run the various LVM commands to add the new space successfully.

So I'm just wondering why sometimes I have to reboot to see the new space to allocate towards LVM and then other times, I don't have to. Granted at work, I know we have SAN and hypervisor, however at home, when working with AWS, I don't know what is on the backend. I would think it would be consistent.

thanks

Responses