Re: [zfs-discuss] Fwd: [osol-announce] IMPT: Do not use SXCE Build 102
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 ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Fwd: [osol-announce] IMPT: Do not use SXCE Build 102
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- ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Fwd: [osol-announce] IMPT: Do not use SXCE Build 102
On Sun, Nov 16, 2008 at 11:44 PM, Jeff Bonwick [EMAIL PROTECTED] 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 ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
