Solaris Volume Manager only supports large volumes (>1 TB) on Solaris 9 4/03 or later when running a 64–bit kernel. Running a system with large volumes under 32–bit kernel on previous Solaris 9 releases will affect Solaris Volume Manager functionality. Specifically, note the following:
If a system with large volumes is rebooted under a 32–bit Solaris 9 4/03 or later kernel, the large volumes will be visible through metastat output, but they cannot be accessed, modified or deleted, and no new large volumes can be created. Any volumes or file systems on a large volume in this situation will also be unavailable.
If a system with large volumes is rebooted under a release of Solaris prior to Solaris 9 4/03, Solaris Volume Manager will not start. All large volumes must be removed before Solaris Volume Manager will run under another version of the Solaris platform.
Solaris Volume Manager transactional volumes do not support large volumes. In all cases, UFS logging should be used. For more information, seemount_ufs(1M).
Do not create large volumes if you expect to run the Solaris software with a 32–bit kernel or if you expect to use a version of the Solaris OS prior to Solaris 9 4/03.