OpenSolaris

1. Community: OS/Net (ON)
   1. Blogs
   2. Development Process
   3. Developer's Reference
      1. Introduction
      2. Prerequisites
      3. The Source Tree, part 1
      4. The Source Tree, part 2
      5. Building OpenSolaris
      6. Installing and Testing OpenSolaris
      7. Integration Procedure
      8. Best Practices and Requirements
      9. Glossary
   4. Discussions
   5. Installation (from source) Quickstart
      1. Annotated nightly(1) Mail Example
   6. Currently Known Issues
   7. CRT
      1. Advocates & Sponsors
      2. Becoming a CRT Advocate
      3. Charter
      4. RTI nits to avoid
      5. Sponsor Tasks
      6. Becoming a Sponsor
   8. Schedule
   9. ONNV Flag Days, Heads Ups, and Project Integration History
      1. All
      2. Builds 91-95
      3. Builds 86-90
      4. Builds 81-85
      5. Builds 76-80
      6. Builds 71-75
      7. Builds 66-70
      8. Builds 61-65
      9. Builds 56-60
      10. Builds 51-55
      11. Builds 46-50
      12. Builds 41-45
      13. Builds 36-40
      14. Builds 31-35
      15. Builds 26-30
      16. Builds 21-25
   10. Leaders
   11. Observers
   12. Putback Logs
   13. Developing Solaris
       1. Quality Death Spiral
   14. wx
   15. findunref and unreferenced files
   16. Bourne/Korn Shell Coding Conventions

Heads up: Builds 86 and 87 are toxic for zfs root

Date: Thu, 03 Apr 2008 16:21:08 -0600
From: Evan Layton <Evan.Layton at sun dot com>
To: onnv-gate at onnv dot eng dot sun dot com
Subject: Heads up: Builds 86 and 87 are toxic for zfs root

If you are not running a ZFS root you can ignore the rest of this message.

Most people are not using zfs root at this time since zfs boot is not yet available.

If you're not sure if you're booted on a zfs root you can quickly tell
by simply running "df -h /".

If you're on zfs the output will look something like:
Filesystem              size   used  avail capacity  Mounted on
rpool/ROOT/opensolaris   19G   2.0G   17G    11%    /

If not it should be more like:
Filesystem             size   used  avail capacity  Mounted on
/dev/dsk/c0t1d0s0       15G   6.1G   8.6G    42%    /


The putback of CR 6664570 introduced a bug in the fs-usr script that
will cause machines with zfs root to fail to boot. A new CR (6684121) has
been filed to track this issue in the smf fs-usr script.

This is a problem for both builds 86 and 87. Build 88 will
introduce the zfs boot project which will resolve this issue.
If you want to bfu to builds 86 and 87 it is necessary to
apply the workaround described below.

There are a few options for working around this issue:
- bfu build 86/87 but apply the smf fix (the edit to fs-usr shown
   below) before rebooting.
- Apply the workaround below, if the machine was rebooted before
   applying the smf fix or you've already hit this problem.

If you attempt to boot zfs root on these builds you will see
errors similar to this example.

/usr/sbin/pmconfig: cannot open/create "/etc/.cpr_config", Bad file number
Apr 3 15:02:05 svc.startd[7]: svc:system/sysevent:default: Method 
"/lib/method/svc-sysevent start" failed with exit status 95.
Apr 3 15:02:05 svc.startd[7]: svc:system/sysevent:default failed fatally: 
transitioning to maintenance (see 'svcs -xv' for more details)
Requesting system Maintenance Mode
(See /lib/svc/share/README for more information.)
Console login service(s) cannot run

Root password for system maintenance (control-d to bypass):


The work around for this is to run "mount -o remount,rw /" while
in maintenance mode then edit /lib/svc/method/fs-usr and change
line 51 from:

if smf_is_globalzone && [ $rootiszfs = 0 ]; then

to:

if smf_is_globalzone; then

Then reboot.