Installation guide

Solaris Volume Manager
The following Solaris Volume Manager bug applies to the Solaris 10 release.
Solaris Volume Manager metattach Command Might
Fail
If you have a Solaris Volume Manager mirrored root (/) le system in which the le system does
not start on cylinder 0, all submirrors you attach must also not start on cylinder 0.
If you attempt to attach a submirror starting on cylinder 0 to a mirror in which the original
submirror does not start on cylinder 0, the following error message is displayed:
can’t attach labeled submirror to an unlabeled mirror
Workaround: Choose one of the following workarounds:
■
Ensure that both the root le system and the volume for the other submirror start on
cylinder 0.
■
Ensure that both the root le system and the volume for the other submirror do not start on
cylinder 0.
Note – By default, the JumpStart installation process starts swap at cylinder 0 and the root (/) le
system somewhere else on the disk. Common system administration practice is to start slice 0 at
cylinder 0. Mirroring a default JumpStart installation with root on slice 0, but not cylinder 0, to
a typical secondary disk with slice 0 that starts at cylinder 0, can cause problems. This mirroring
results in an error message when you attempt to attach the second submirror. For more
information about the default behavior of Solaris installation programs, see the Solaris 10
Installation Guides.
Sun Java Desktop System
This section describes issues that apply to the Sun Java Desktop System (Java DS) in the Solaris
10 OS.
Email and Calendar
This section describes issues related to Email and Calendars.
Solaris Volume Manager
Solaris 10 10/09 Release Notes • October 200994