zfs discuss - Nov 2008 - Fwd: [osol-announce] IMPT: Do not use SXCE Build 102

Heads up! and apologies to folks subscribed to os-announce.


---------- Forwarded message ----------
From: Derek Cicero <Derek.Cicero at sun.com>
Date: Sat, Nov 15, 2008 at 1:14 PM
Subject: [osol-announce] IMPT: Do not use SXCE Build 102
To: opensolaris-announce at opensolaris.org, os-discuss
<opensolaris-discuss at opensolaris.org>


Due to the following bug, I have removed build 102 from the Download page.

 6771840 zpool online on ZFS root can panic system

It apparently may cause data corruption and may have been implicated in
damage to one or more systems that have upgraded to build 102 or
beyond.

We will remove it from the SDLC on Monday. I will notify about the
schedule for a repsin.

Derek


--
Derek Cicero
Program Manager
Solaris Kernel Group, Software Division
_______________________________________________
opensolaris-announce mailing list
opensolaris-announce at opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/opensolaris-announce



-- 
Al Hopper  Logical Approach Inc,Plano,TX al at logical-approach.com
                   Voice: 972.379.2133 Timezone: US CDT
OpenSolaris Governing Board (OGB) Member - Apr 2005 to Mar 2007
http://www.opensolaris.org/os/community/ogb/ogb_2005-2007/

On Sat, Nov 15, 2008 at 05:41:56PM -0600, Al Hopper
wrote:
> Heads up! and apologies to folks subscribed to os-announce.
Argh, and I just live-upgraded to build 102.  I searched for this bug
number in three bug databases without success.  Does it affect ZFS
root only, as long as I don''t use `offline'' or
`online''?  Do I have
to boot back to 101?
> ---------- Forwarded message ----------
> From: Derek Cicero <Derek.Cicero at sun.com>
> Date: Sat, Nov 15, 2008 at 1:14 PM
> Subject: [osol-announce] IMPT: Do not use SXCE Build 102
> To: opensolaris-announce at opensolaris.org, os-discuss
> <opensolaris-discuss at opensolaris.org>
> 
> Due to the following bug, I have removed build 102 from the Download page.
> 
>  6771840 zpool online on ZFS root can panic system
> 
> It apparently may cause data corruption and may have been implicated in
> damage to one or more systems that have upgraded to build 102 or
> beyond.
-- 
-Gary Mills-    -Unix Support-    -U of M Academic Computing and Networking-

These are the conditions:

(1) The bug is specific to the root pool.  Other pools are unaffected.
(2) It is triggered by doing a ''zpool online'' while I/O is in
flight.
(3) Item (2) can be triggered by syseventd.
(4) The bug is new in build 102.  Builds 101 and earlier are fine.

I believe the following should be a viable workaround until build 103:

(1) svcadm disable -t sysevent
(2) Don''t run zpool online on your root pool

Jeff

On Sun, Nov 16, 2008 at 03:12:03PM -0600, Gary Mills
wrote:
> On Sat, Nov 15, 2008 at 05:41:56PM -0600, Al Hopper wrote:
> > Heads up! and apologies to folks subscribed to os-announce.
> 
> Argh, and I just live-upgraded to build 102.  I searched for this bug
> number in three bug databases without success.  Does it affect ZFS
> root only, as long as I don''t use `offline'' or
`online''?  Do I have
> to boot back to 101?
> 
> > ---------- Forwarded message ----------
> > From: Derek Cicero <Derek.Cicero at sun.com>
> > Date: Sat, Nov 15, 2008 at 1:14 PM
> > Subject: [osol-announce] IMPT: Do not use SXCE Build 102
> > To: opensolaris-announce at opensolaris.org, os-discuss
> > <opensolaris-discuss at opensolaris.org>
> > 
> > Due to the following bug, I have removed build 102 from the Download
page.
> > 
> >  6771840 zpool online on ZFS root can panic system
> > 
> > It apparently may cause data corruption and may have been implicated
in
> > damage to one or more systems that have upgraded to build 102 or
> > beyond.
> 
> -- 
> -Gary Mills-    -Unix Support-    -U of M Academic Computing and
Networking-
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

On Sun, Nov 16, 2008 at 11:44 PM, Jeff Bonwick <Jeff.Bonwick at sun.com>
wrote:
> These are the conditions:
>
> (1) The bug is specific to the root pool.  Other pools are unaffected.
> (2) It is triggered by doing a ''zpool online'' while I/O
is in flight.
> (3) Item (2) can be triggered by syseventd.
> (4) The bug is new in build 102.  Builds 101 and earlier are fine.
>
> I believe the following should be a viable workaround until build 103:
>
> (1) svcadm disable -t sysevent
> (2) Don''t run zpool online on your root pool
>
> Jeff
>

Hi Jeff,

Thank you for the details.  A few more questions:  Does booting into build
102 do I zpool online on the root pool? And the above disable -t is
"temporary" till the next reboot - any specific reason for doing it
that
way?  And last question:  What do I loose when I disable "sysevent"?

Thank you,
  _Johan



-- 
Any sufficiently advanced technology is indistinguishable from magic.
   Arthur C. Clarke

My blog: http://initialprogramload.blogspot.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20081117/ca242b2a/attachment.html>

Does this affect a fresh install into a single, full disk pool?  I just did this
with
nv102 on my laptop.  So far, it seems to be working ...
Unfortunately, this would be a pain to unwind.  Is there a quick fix
binary patch available?

The only thing that appears to have broken is resume.  Could this be
related?  Suspend/resume used to work on nv99 and the only thing that
is different is that I''m now migrated to ZFS boot.

George
-- 
This message posted from opensolaris.org

On Mon, Nov 17, 2008 at 07:27:50AM +0200, Johan Hartzenberg
wrote:
> 
>    Thank you for the details.  A few more questions:  Does booting into
>    build 102 do I zpool online on the root pool? And the above disable -t
>    is "temporary" till the next reboot - any specific reason for
doing it
>    that way?  And last question:  What do I loose when I disable
>    "sysevent"?
I can answer that last one, since I tried it.  When you reboot without
sysevent, you will find that the console login service cannot run.
You''ll wind up in single-user mode.  You can enable sysevent at that
point and reboot again.  Disabling it with `-t'' after the
system''s up
seems to do no harm.

-- 
-Gary Mills-    -Unix Support-    -U of M Academic Computing and Networking-