Installation guide

4.6.4.7 Verify Fails on Dual-Mounted Domain

While running verify on a dual-mounted domain, it is possible to receive

the following type of message:

Corruption in frag file type list for frag type 0

Expected to find set ID 36f68cbd.0006ae8c.1.8001 but found set ID

36f68c94.000b1b83.1.8001

This message can be ignored as it does not reﬂect an actual problem in the

frag ﬁle, but instead an artifact of the dual-mounted domain.

4.6.4.8 Very Small AdvFS Domains Created In lockmode 4

Creation of domains smaller than 20 MB while running in lockmode 4 can

cause the system to panic when the ﬁrst ﬁleset is created within the small

domain. Such domains may safely be created and used if the system is not

running in lockmode 4. To see which lockmode the system is running in,

enter the following command:

% sysconfig -q generic lockmode

4.6.5 Logical Storage Manager

The following notes describe problems and restrictions of the Logical Storage

Manager (LSM).

4.6.5.1 LSM Sparse Plexes May Erroneously Mask an I/O Failure

Under certain hardware failure scenarios, an LSM volume conﬁgured with a

sparse plex may erroneously return success to the ﬁle system or application

when in fact the I/O failed. This does not occur when you do not conﬁgure

volumes with sparse plexes.

4.6.5.2 Restrictions with LSM root and swap Volumes

Root, primary swap, and secondary swap volumes conﬁgured under LSM

have the following restrictions:

• Root and primary swap must be on the same physical disk and you must

conﬁgure them using the encapsulation tools.

• If a secondary swap volume is conﬁgured under LSM, you must

conﬁgure the root and primary swap.

• You must conﬁgure the root, primary swap, and any secondary swap

volumes into the disk group named rootdg.

4–38 Base System Software Notes