False. The LVM RAID 0/1 solution requires the use of Distributed volumes . The smallest "stripe" size for a Distributed volume is the smallest size of an LVM extent = 1MB. This does not equate to the average block size of commonly used OS/applications.
A2:
False. The pvcreate “B <rdsk> command simply reserves the space on disk to store a LIF area and BDRA . It is the mkboot command that makes a disk bootable.
A3:
False. LVM Physical Volume Groups and PVG -strictness offer the administrator the opportunity to configure mirroring in such a way that mirrored data is housed on disks attached to a separate controller/interface card. The way in which the PVGs have been configured will determine whether the solution offers such separation of data and mirrored data. It is possible to configure a PVG -strict solution that contravenes this requirement.
A4:
False. It is important to have the "hpux “lq" boot command on all disks in the mirror configuration. If the "hpux “lq" boot command is stored only on the first disk and that disk fails, the other disks in the volume group may not be able to achieve an LVM quorum and the system will not be able to boot. It is important that the "hpux “lq" boot command is stored on all disks in the mirror configuration.
A5:
False. Nowhere in the question does it mention that the disk will be exchanged/replaced. Even if they where replaced , the vgscan command is used to repair problems with the /etc/lvmtab file. To repair the corrupt/lost PVRA/ VGRA disk headers, we use the vgcfgrestore command.
