When a GPT Disk is re-sized, the private region does not need to move and so there is no header update. When a volume is re-sized, this gets written into the private region - again, does not require a header update. When a rescan is initiated, the header is read from the disk and loaded into memory. As the header contains the old public region size, the disk appears to revert to its former size. The expanded volume is now bigger than the public region and the volume will go missing as it is smaller than its contents.
This fix specifically addresses the problem identified above. It has not been fully tested and should be applied in a test environment before placing into production. If the systems are not critically impaired, it is recommended to delay the installation of this private fix until the next scheduled maintenance release. Before applying this private fix, systems may be required to be upgraded to the latest code base. The support representative will help in determining the best course of action.
0 comments:
Post a Comment