24.05.2014 Views

AIX Version 4.3 Differences Guide

AIX Version 4.3 Differences Guide

AIX Version 4.3 Differences Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

extended to 511 logical volumes and 128 physical volumes by specifying the -B<br />

flag.<br />

5.6.3 Small VG to Big VG Conversion<br />

To convert the small VG to a big VG, a number of free physical partitions are<br />

needed to expand the VGDA/VGSA. Depending on the size of the physical<br />

partition and the current size of the VGDA, the number of partitions required are<br />

calculated. Since the first partition starts immediately after the end of the<br />

secondary VGDA, if it is occupied by a logical partition, it will be migrated to<br />

another free physical partition on the disk. This first physical partition will then be<br />

removed from the list of available partitions (not be moved or allocated for any<br />

reason), and the remaining partitions will be renumbered. After the conversion,<br />

the total number of physical partitions on the disk will not change, except that the<br />

extra partitions allocated for the VGDA are marked non allocatable.<br />

You should be aware of the following items when you perform a conversion from<br />

a small VG to a big VG:<br />

• All the disks in the volume group should have enough free PPs for the<br />

conversion to be possible.<br />

• All the logical volumes in the volume group must be in closed/synced state.<br />

• All physical volumes must be available and be in the ACTIVE state.<br />

• The volume group is varied on in management mode to prevent opening of<br />

any logical volumes.<br />

• The ownership/permissions of special device files will only be preserved if mklv<br />

or chlv are used with the -U, -G, or -P flags.<br />

Currently, the migratepv command does not allow the migration of individual<br />

physical partitions. The conversion needs to free up just enough physical<br />

partitions from the beginning of the disk to elsewhere. The current<br />

implementation will try to migrate the partitions within the physical volume, and<br />

the user must move the partitions to other disks in the volume group.<br />

5.6.4 Big VG Limitations<br />

The following list are the limitations of a big VG:<br />

• A big VG is not enabled for concurrent access. This is posed by the<br />

communication path used by the concurrent logical volumes. It will be<br />

prohibitively slower for the big VG to communicate across nodes due to an<br />

increase in the number of disks.<br />

• The rootvg cannot be converted to the big VG format.<br />

• A big VG cannot be imported or activated on pre-<strong>AIX</strong> <strong>4.3</strong>.2 levels.<br />

5.7 Concurrent Online Mirror Backup and Special File Support (<strong>4.3</strong>.2)<br />

<strong>AIX</strong> <strong>4.3</strong>.1 provided support for an on-line backup mechanism for a mirrored raw<br />

logical volume. But it lacked support for file system access and restricts<br />

concurrent mode access for the volume group.<br />

<strong>AIX</strong> <strong>4.3</strong>.2 enhances the capabilities of the online backup in <strong>AIX</strong> <strong>4.3</strong> to support:<br />

92 <strong>AIX</strong> <strong>Version</strong> <strong>4.3</strong> <strong>Differences</strong> <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!