From sacadmin Fri Jun 18 18:52:47 2010 Received: from sac.sfbay.sun.com (localhost [127.0.0.1]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id o5J1qlw9020981; Fri, 18 Jun 2010 18:52:47 -0700 (PDT) Received: (from cindi@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id o5J1qlg3020977; Fri, 18 Jun 2010 18:52:47 -0700 (PDT) Date: Fri, 18 Jun 2010 18:52:47 -0700 (PDT) From: Cynthia McGuire Message-Id: <201006190152.o5J1qlg3020977@sac.sfbay.sun.com> To: PSARC-record@sac.sfbay.sun.com, psarc-ext@sun.com Cc: fma-core@sun.com Subject: Solaris Instance UUID [PSARC/2010/226 FastTrack timeout 06/25/2010] Status: RO Content-Length: 593 Template Version: @(#)sac_nextcase 1.70 03/30/10 SMI This information is Copyright (c) 2010, Oracle and/or its affiliates. All rights reserved. 1. Introduction 1.1. Project/Component Working Name: Solaris Instance UUID 1.2. Name of Document Author/Supplier: Author: Gavin Maltby 1.3 Date of This Document: 18 June, 2010 4. Technical Description See the case directory for more detail 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: ON 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open From cindi@sac.sfbay.sun.com Fri Jun 18 18:52:50 2010 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id o5J1qoIZ020988 for ; Fri, 18 Jun 2010 18:52:50 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail2sca.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id o5J1qo3b011898; Fri, 18 Jun 2010 18:52:50 -0700 (PDT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0L4800E01NW2VC00@nwk-avmta-2.sfbay.sun.com>; Fri, 18 Jun 2010 18:52:50 -0700 (PDT) Received: from dm-sfbay-02.sfbay.sun.com ([129.146.11.31]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0L480069SNW1NC80@nwk-avmta-2.sfbay.sun.com>; Fri, 18 Jun 2010 18:52:49 -0700 (PDT) Received: from sac.sfbay.sun.com (sac.SFBay.Sun.COM [129.146.226.132]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id o5J1qmut022293; Fri, 18 Jun 2010 18:52:48 -0700 (PDT) Received: from sac.sfbay.sun.com (localhost [127.0.0.1]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id o5J1qlw9020981; Fri, 18 Jun 2010 18:52:47 -0700 (PDT) Received: (from cindi@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id o5J1qlg3020977; Fri, 18 Jun 2010 18:52:47 -0700 (PDT) Date: Fri, 18 Jun 2010 18:52:47 -0700 (PDT) From: Cynthia McGuire Subject: Solaris Instance UUID [PSARC/2010/226 FastTrack timeout 06/25/2010] To: PSARC-record@sac.sfbay.sun.com, psarc-ext@sun.com Cc: fma-core@sun.com Message-id: <201006190152.o5J1qlg3020977@sac.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 593 Template Version: @(#)sac_nextcase 1.70 03/30/10 SMI This information is Copyright (c) 2010, Oracle and/or its affiliates. All rights reserved. 1. Introduction 1.1. Project/Component Working Name: Solaris Instance UUID 1.2. Name of Document Author/Supplier: Author: Gavin Maltby 1.3 Date of This Document: 18 June, 2010 4. Technical Description See the case directory for more detail 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: ON 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open From sacadmin Sat Jun 19 13:32:58 2010 Received: from dm-sfbay-01.sfbay.sun.com (dm-sfbay-01.SFBay.Sun.COM [129.145.155.118]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id o5JKWwwO028587; Sat, 19 Jun 2010 13:32:58 -0700 (PDT) Received: from sca-ea-mail-4.sun.com (sca-ea-mail-4.Sun.COM [192.18.43.22]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id o5JKWw2K015623; Sat, 19 Jun 2010 13:32:58 -0700 (PDT) Received: from relay41i.sun.com ([192.5.209.70]) by sca-ea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id o5JKWwG7003247; Sat, 19 Jun 2010 20:32:58 GMT Received: from mmp41es.mmp.us.syntegra.com ([160.41.221.10] [160.41.221.10]) by relay41i.sun.com with ESMTP id BT-MMP-474419; Sat, 19 Jun 2010 20:32:57 Z Received: from relay41i.sun.com (relay41i.sun.com [192.5.209.70]) by mmp41es.mmp.us.syntegra.com with ESMTP id BT-MMP-9460095; Sat, 19 Jun 2010 20:32:57 Z Received: from carlson.workingcode.com ([75.150.68.97] [75.150.68.97]) by relay4i.sun.com with ESMTP id BT-MMP-22943524; Sat, 19 Jun 2010 20:32:56 Z Received: from dhcp-226.workingcode.com (dhcp-226 [192.168.254.226]) (authenticated bits=0) by carlson.workingcode.com (8.14.2+Sun/8.14.4) with ESMTP id o5JKWuae021197 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 19 Jun 2010 16:32:56 -0400 (EDT) Message-ID: <4C1D2978.20605@workingcode.com> Date: Sat, 19 Jun 2010 16:32:56 -0400 From: James Carlson User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 To: Cynthia McGuire CC: PSARC-record@sac.sfbay.sun.com, psarc-ext@sun.com, fma-core@sun.com Subject: Re: Solaris Instance UUID [PSARC/2010/226 FastTrack timeout 06/25/2010] References: <201006190152.o5J1qlg3020977@sac.sfbay.sun.com> In-Reply-To: <201006190152.o5J1qlg3020977@sac.sfbay.sun.com> X-Brightmail-Tracker: AAAAAA== X-Enigmail-Version: 1.0.1 X-DCC-INFN-TO-Metrics: carlson; whitelist X-Antispam: No, score=0.0/5.0, scanned in 0.210sec at (localhost [127.0.0.1]) by smf-spamd v1.3.1 - http://smfs.sf.net/ MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Status: RO Content-Length: 474 On 6/18/10 9:52 PM, Cynthia McGuire wrote: > > Template Version: @(#)sac_nextcase 1.70 03/30/10 SMI > This information is Copyright (c) 2010, Oracle and/or its affiliates. All rights reserved. Seem to be missing some content here ... did you perhaps forget to forward something? For what it's worth, there's already a UUID in use in Zones to identify Solaris instances. Is this another UUID? -- James Carlson 42.703N 71.076W From carlsonj@workingcode.com Sat Jun 19 13:32:59 2010 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id o5JKWxIr028591 for ; Sat, 19 Jun 2010 13:32:59 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail2sca.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id o5JKWxq9014767 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Sat, 19 Jun 2010 13:32:59 -0700 (PDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0L4A006033QY3A00@brm-avmta-1.central.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Sat, 19 Jun 2010 14:32:58 -0600 (MDT) Received: from sca-ea-mail-4.sun.com ([192.18.43.22]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0L4A00J8Z3QY7NB0@brm-avmta-1.central.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Sat, 19 Jun 2010 14:32:58 -0600 (MDT) Received: from relay42i.sun.com ([192.5.209.72]) by sca-ea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id o5JKPqNS002084 for ; Sat, 19 Jun 2010 20:32:57 +0000 (GMT) Received: from mmp41es.mmp.us.syntegra.com ([160.41.221.10] [160.41.221.10]) by relay42i.sun.com with ESMTP id BT-MMP-474163; Sat, 19 Jun 2010 20:32:57 +0000 (Z) Received: from relay41i.sun.com (relay41i.sun.com [192.5.209.70]) by mmp41es.mmp.us.syntegra.com with ESMTP id BT-MMP-9460095; Sat, 19 Jun 2010 20:32:57 +0000 (Z) Received: from carlson.workingcode.com ([75.150.68.97] [75.150.68.97]) by relay4i.sun.com with ESMTP id BT-MMP-22943524; Sat, 19 Jun 2010 20:32:56 +0000 (Z) Received: from dhcp-226.workingcode.com (dhcp-226 [192.168.254.226]) (authenticated bits=0) by carlson.workingcode.com (8.14.2+Sun/8.14.4) with ESMTP id o5JKWuae021197 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 19 Jun 2010 16:32:56 -0400 (EDT) Date: Sat, 19 Jun 2010 16:32:56 -0400 From: James Carlson Subject: Re: Solaris Instance UUID [PSARC/2010/226 FastTrack timeout 06/25/2010] In-reply-to: <201006190152.o5J1qlg3020977@sac.sfbay.sun.com> To: Cynthia McGuire Cc: PSARC-record@sac.sfbay.sun.com, psarc-ext@sun.com, fma-core@sun.com Message-id: <4C1D2978.20605@workingcode.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 X-Brightmail-Tracker: AAAAAA== X-Enigmail-Version: 1.0.1 X-DCC-INFN-TO-Metrics: carlson; whitelist X-Antispam: No, score=0.0/5.0, scanned in 0.210sec at (localhost [127.0.0.1]) by smf-spamd v1.3.1 - http://smfs.sf.net/ References: <201006190152.o5J1qlg3020977@sac.sfbay.sun.com> User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 Status: RO Content-Length: 474 On 6/18/10 9:52 PM, Cynthia McGuire wrote: > > Template Version: @(#)sac_nextcase 1.70 03/30/10 SMI > This information is Copyright (c) 2010, Oracle and/or its affiliates. All rights reserved. Seem to be missing some content here ... did you perhaps forget to forward something? For what it's worth, there's already a UUID in use in Zones to identify Solaris instances. Is this another UUID? -- James Carlson 42.703N 71.076W From sacadmin Sat Jun 19 22:35:57 2010 Received: from dm-sfbay-01.sfbay.sun.com (dm-sfbay-01.SFBay.Sun.COM [129.145.155.118]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id o5K5Zvgu003731; Sat, 19 Jun 2010 22:35:57 -0700 (PDT) Received: from brmea-mail-2.sun.com (brmea-mail-2.Sun.COM [192.18.98.43]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id o5K5ZuKe000490; Sat, 19 Jun 2010 22:35:56 -0700 (PDT) Received: from rcsinet13.oracle.com (rcsinet13.oracle.com [148.87.113.125]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id o5K5ZuSC019732; Sun, 20 Jun 2010 05:35:56 GMT Received: from acsmt354.oracle.com (acsmt354.oracle.com [141.146.40.154]) by rcsinet13.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o5K1Sip7029959; Sun, 20 Jun 2010 05:35:53 GMT Received: from abhmt006.oracle.com by acsmt353.oracle.com with ESMTP id 341414131277012102; Sat, 19 Jun 2010 22:35:02 -0700 Received: from tara.local (/10.7.250.215) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Sat, 19 Jun 2010 22:35:02 -0700 Message-ID: <4C1DA9DE.9060409@oracle.com> Date: Sat, 19 Jun 2010 22:40:46 -0700 From: Cynthia McGuire User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228) MIME-Version: 1.0 To: James Carlson CC: Cynthia McGuire , PSARC-record@sac.sfbay.sun.com, psarc-ext@sun.com, fma-core@sun.com Subject: Re: Solaris Instance UUID [PSARC/2010/226 FastTrack timeout 06/25/2010] References: <201006190152.o5J1qlg3020977@sac.sfbay.sun.com> <4C1D2978.20605@workingcode.com> In-Reply-To: <4C1D2978.20605@workingcode.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Source-IP: acsmt354.oracle.com [141.146.40.154] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A090202.4C1DA8BA.00D0:SCFMA4539814,ss=1,fgs=0 Status: RO Content-Length: 619 As per the e-mail, see the case directory for the full text. http://arc.opensolaris.org/caselog/PSARC/2010/226/mail Cindi James Carlson wrote: > On 6/18/10 9:52 PM, Cynthia McGuire wrote: >> Template Version: @(#)sac_nextcase 1.70 03/30/10 SMI >> This information is Copyright (c) 2010, Oracle and/or its affiliates. All rights reserved. > > Seem to be missing some content here ... did you perhaps forget to > forward something? > > For what it's worth, there's already a UUID in use in Zones to identify > Solaris instances. Is this another UUID? > -- Cynthia McGuire, Fishworks http://blogs.sun.com/cindi From cynthia.mcguire@oracle.com Sat Jun 19 22:35:58 2010 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id o5K5ZwAS003735 for ; Sat, 19 Jun 2010 22:35:58 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail3mpk.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id o5K5Zwe3012385; Sat, 19 Jun 2010 22:35:58 -0700 (PDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0L4A00D01SVX7W00@brm-avmta-1.central.sun.com>; Sat, 19 Jun 2010 23:35:57 -0600 (MDT) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0L4A0056PSVXFZA0@brm-avmta-1.central.sun.com>; Sat, 19 Jun 2010 23:35:57 -0600 (MDT) Received: from rcsinet13.oracle.com (rcsinet13.oracle.com [148.87.113.125]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id o5K5ZuSC019732; Sun, 20 Jun 2010 05:35:56 +0000 (GMT) Received: from acsmt354.oracle.com (acsmt354.oracle.com [141.146.40.154]) by rcsinet13.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o5K1Sip7029959; Sun, 20 Jun 2010 05:35:53 +0000 (GMT) Received: from abhmt006.oracle.com by acsmt353.oracle.com with ESMTP id 341414131277012102; Sat, 19 Jun 2010 22:35:02 -0700 Received: from tara.local (/10.7.250.215) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Sat, 19 Jun 2010 22:35:02 -0700 Date: Sat, 19 Jun 2010 22:40:46 -0700 From: Cynthia McGuire Subject: Re: Solaris Instance UUID [PSARC/2010/226 FastTrack timeout 06/25/2010] In-reply-to: <4C1D2978.20605@workingcode.com> To: James Carlson Cc: Cynthia McGuire , PSARC-record@sac.sfbay.sun.com, psarc-ext@sun.com, fma-core@sun.com Message-id: <4C1DA9DE.9060409@oracle.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 X-Source-IP: acsmt354.oracle.com [141.146.40.154] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A090202.4C1DA8BA.00D0:SCFMA4539814,ss=1,fgs=0 References: <201006190152.o5J1qlg3020977@sac.sfbay.sun.com> <4C1D2978.20605@workingcode.com> User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228) Status: RO Content-Length: 619 As per the e-mail, see the case directory for the full text. http://arc.opensolaris.org/caselog/PSARC/2010/226/mail Cindi James Carlson wrote: > On 6/18/10 9:52 PM, Cynthia McGuire wrote: >> Template Version: @(#)sac_nextcase 1.70 03/30/10 SMI >> This information is Copyright (c) 2010, Oracle and/or its affiliates. All rights reserved. > > Seem to be missing some content here ... did you perhaps forget to > forward something? > > For what it's worth, there's already a UUID in use in Zones to identify > Solaris instances. Is this another UUID? > -- Cynthia McGuire, Fishworks http://blogs.sun.com/cindi From sacadmin Sun Jun 20 15:27:56 2010 Received: from jurassic.Eng.Sun.COM (jurassic.SFBay.Sun.COM [129.146.17.59]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id o5KMRueu001927; Sun, 20 Jun 2010 15:27:56 -0700 (PDT) Received: from xanadu (xanadu.SFBay.Sun.COM [129.146.228.194]) by jurassic.Eng.Sun.COM (8.14.4+Sun/8.14.4) with ESMTP id o5KMRtDW346566; Sun, 20 Jun 2010 15:27:55 -0700 (PDT) Date: Sun, 20 Jun 2010 15:27:55 -0700 From: Dan Price To: Cynthia McGuire Cc: PSARC-record@sac.sfbay.sun.com, psarc-ext@sun.com, fma-core@sun.com, daniel.price@oracle.com Subject: Re: Solaris Instance UUID [PSARC/2010/226 FastTrack timeout 06/25/2010] Message-ID: <20100620222732.GA12378@xanadu.sfbay.sun.com> References: <201006190152.o5J1qlg3020977@sac.sfbay.sun.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201006190152.o5J1qlg3020977@sac.sfbay.sun.com> User-Agent: Mutt/1.5.20 (2009-06-14) Status: RO Content-Length: 1368 On Fri 18 Jun 2010 at 06:52PM, Cynthia McGuire wrote: > > Template Version: @(#)sac_nextcase 1.70 03/30/10 SMI > This information is Copyright (c) 2010, Oracle and/or its affiliates. All rights reserved. > 1. Introduction > 1.1. Project/Component Working Name: > Solaris Instance UUID > 1.2. Name of Document Author/Supplier: > Author: Gavin Maltby > 1.3 Date of This Document: > 18 June, 2010 > 4. Technical Description > See the case directory for more detail This case might be easier to grok if it was called "crash dump UUID" or "boot UUID" or some such-- "image UUID" seems vague, and this case doesn't appear to be generating anything which is scoped beyond the use case of crash dumps and live dumps (which seems perfectly reasonable). I presume when you say "UUID" you are stating that the UUID will comply with some particular standard? RFC 4122? My big question, thought, is "Why log it to syslog?" The case provides no rationale for this and seems to tempt customers to consume it-- especially as it marks the log message itself as "committed", which seemed surprising to me. There may be other committed syslog messages but I don't know of them, and it seems like this would be something to avoid (i.e. log messages are not an interface). -dp -- Daniel Price, Solaris Kernel Engineering http://blogs.sun.com/dp From daniel.price@oracle.com Sun Jun 20 15:27:57 2010 Received: from sunmail6brm.central.sun.com (sunmail6brm.Central.Sun.COM [129.147.4.169]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id o5KMRvvt001931 for ; Sun, 20 Jun 2010 15:27:57 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail6brm.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id o5KMRvAL018046; Sun, 20 Jun 2010 17:27:57 -0500 (CDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0L4C008013QLSC00@brm-avmta-1.central.sun.com>; Sun, 20 Jun 2010 16:27:57 -0600 (MDT) Received: from jurassic.Eng.Sun.COM ([129.146.17.63]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0L4C00M4Y3QKFID0@brm-avmta-1.central.sun.com>; Sun, 20 Jun 2010 16:27:56 -0600 (MDT) Received: from xanadu (xanadu.SFBay.Sun.COM [129.146.228.194]) by jurassic.Eng.Sun.COM (8.14.4+Sun/8.14.4) with ESMTP id o5KMRtDW346566; Sun, 20 Jun 2010 15:27:55 -0700 (PDT) Date: Sun, 20 Jun 2010 15:27:55 -0700 From: Dan Price Subject: Re: Solaris Instance UUID [PSARC/2010/226 FastTrack timeout 06/25/2010] In-reply-to: <201006190152.o5J1qlg3020977@sac.sfbay.sun.com> To: Cynthia McGuire Cc: PSARC-record@sac.sfbay.sun.com, psarc-ext@sun.com, fma-core@sun.com, daniel.price@oracle.com Message-id: <20100620222732.GA12378@xanadu.sfbay.sun.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-PMX-Version: 5.4.1.325704 References: <201006190152.o5J1qlg3020977@sac.sfbay.sun.com> User-Agent: Mutt/1.5.20 (2009-06-14) Status: RO Content-Length: 1368 On Fri 18 Jun 2010 at 06:52PM, Cynthia McGuire wrote: > > Template Version: @(#)sac_nextcase 1.70 03/30/10 SMI > This information is Copyright (c) 2010, Oracle and/or its affiliates. All rights reserved. > 1. Introduction > 1.1. Project/Component Working Name: > Solaris Instance UUID > 1.2. Name of Document Author/Supplier: > Author: Gavin Maltby > 1.3 Date of This Document: > 18 June, 2010 > 4. Technical Description > See the case directory for more detail This case might be easier to grok if it was called "crash dump UUID" or "boot UUID" or some such-- "image UUID" seems vague, and this case doesn't appear to be generating anything which is scoped beyond the use case of crash dumps and live dumps (which seems perfectly reasonable). I presume when you say "UUID" you are stating that the UUID will comply with some particular standard? RFC 4122? My big question, thought, is "Why log it to syslog?" The case provides no rationale for this and seems to tempt customers to consume it-- especially as it marks the log message itself as "committed", which seemed surprising to me. There may be other committed syslog messages but I don't know of them, and it seems like this would be something to avoid (i.e. log messages are not an interface). -dp -- Daniel Price, Solaris Kernel Engineering http://blogs.sun.com/dp From sacadmin Mon Jun 21 00:07:20 2010 Received: from dm-sfbay-01.sfbay.sun.com (dm-sfbay-01.SFBay.Sun.COM [129.145.155.118]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id o5L77K1h009427; Mon, 21 Jun 2010 00:07:20 -0700 (PDT) Received: from sca-ea-mail-4.sun.com (sca-ea-mail-4.Sun.COM [192.18.43.22]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id o5L77Krb022763; Mon, 21 Jun 2010 00:07:20 -0700 (PDT) Received: from rcsinet15.oracle.com (rcsinet15.oracle.com [148.87.113.117]) by sca-ea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id o5L77KRu010743; Mon, 21 Jun 2010 07:07:20 GMT Received: from acsmt353.oracle.com (acsmt353.oracle.com [141.146.40.153]) by rcsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o5L77HUC022494; Mon, 21 Jun 2010 07:07:18 GMT Received: from abhmt016.oracle.com by acsmt354.oracle.com with ESMTP id 359081801277104035; Mon, 21 Jun 2010 00:07:15 -0700 Received: from [129.150.12.118] (/129.150.12.118) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 21 Jun 2010 00:07:12 -0700 Message-ID: <4C1F0F98.4000802@oracle.com> Date: Mon, 21 Jun 2010 17:07:04 +1000 From: Gavin Maltby Organization: Oracle Corporation User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.1.9) Gecko/20100524 Lightning/1.0b1 Thunderbird/3.0.4 MIME-Version: 1.0 To: Dan Price CC: Cynthia McGuire , PSARC-record@sac.sfbay.sun.com, psarc-ext@sun.com, fma-core@sun.com Subject: Re: Solaris Instance UUID [PSARC/2010/226 FastTrack timeout 06/25/2010] References: <201006190152.o5J1qlg3020977@sac.sfbay.sun.com> <20100620222732.GA12378@xanadu.sfbay.sun.com> In-Reply-To: <20100620222732.GA12378@xanadu.sfbay.sun.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Source-IP: acsmt353.oracle.com [141.146.40.153] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A090202.4C1F0FA7.00DB:SCFMA4539814,ss=1,fgs=0 Status: RO Content-Length: 2575 On 06/21/10 08:27 AM, Dan Price wrote: > On Fri 18 Jun 2010 at 06:52PM, Cynthia McGuire wrote: >> >> Template Version: @(#)sac_nextcase 1.70 03/30/10 SMI >> This information is Copyright (c) 2010, Oracle and/or its affiliates. All rights reserved. >> 1. Introduction >> 1.1. Project/Component Working Name: >> Solaris Instance UUID >> 1.2. Name of Document Author/Supplier: >> Author: Gavin Maltby >> 1.3 Date of This Document: >> 18 June, 2010 >> 4. Technical Description >> See the case directory for more detail > > This case might be easier to grok if it was called "crash dump UUID" > or "boot UUID" or some such-- "image UUID" seems vague, and this case > doesn't appear to be generating anything which is scoped beyond the use > case of crash dumps and live dumps (which seems perfectly reasonable). I'm mostly interested in crash dumps, so I don't mind renaming it as such. There are times in service when it is valuable to ask a customer to collect a bunch of info while the problem is experienced, which might or might not included a forced crash dump or live savecore. For those purposes it can be useful to have label under which such information can go, and that is what the instance uuid can provide. In cases where there have been a few reboots/crashes it can be a real mess trying to correlate which observations came from where. > I presume when you say "UUID" you are stating that the UUID will comply > with some particular standard? RFC 4122? Yes; thought I remembered adding that but it may be to a related FMA portfolio. > My big question, thought, is "Why log it to syslog?" The case provides > no rationale for this and seems to tempt customers to consume it-- > especially as it marks the log message itself as "committed", which > seemed surprising to me. There may be other committed syslog messages > but I don't know of them, and it seems like this would be something > to avoid (i.e. log messages are not an interface). I have no need to log it to syslog for the immediate use in mind. I figured that for the kind of service data collection scenarios mentioned above that a record of the instance UUID would be useful. When you're performing some post-mortem panic analysis it can be useful to correlate messages with the particular panic. So I think that logging it has it uses. I made it Committed because its unlikely ever to have to evolve, and anyone trawling it out of messages files can rely on its structure. I was being generous there - I don't mind dropping the stability level. Thanks Gavin From gavin.maltby@oracle.com Mon Jun 21 00:07:22 2010 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id o5L77MWQ009611 for ; Mon, 21 Jun 2010 00:07:22 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.4) with ESMTP id o5L77Lmi049357; Mon, 21 Jun 2010 01:07:21 -0600 (MDT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0L4C00015RS9QL00@nwk-avmta-1.sfbay.Sun.COM>; Mon, 21 Jun 2010 00:07:21 -0700 (PDT) Received: from sca-ea-mail-4.sun.com ([192.18.43.22]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0L4C00FVARS8EP60@nwk-avmta-1.sfbay.Sun.COM>; Mon, 21 Jun 2010 00:07:20 -0700 (PDT) Received: from rcsinet15.oracle.com (rcsinet15.oracle.com [148.87.113.117]) by sca-ea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id o5L77KRu010743; Mon, 21 Jun 2010 07:07:20 +0000 (GMT) Received: from acsmt353.oracle.com (acsmt353.oracle.com [141.146.40.153]) by rcsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o5L77HUC022494; Mon, 21 Jun 2010 07:07:18 +0000 (GMT) Received: from abhmt016.oracle.com by acsmt354.oracle.com with ESMTP id 359081801277104035; Mon, 21 Jun 2010 00:07:15 -0700 Received: from [129.150.12.118] (/129.150.12.118) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 21 Jun 2010 00:07:12 -0700 Date: Mon, 21 Jun 2010 17:07:04 +1000 From: Gavin Maltby Subject: Re: Solaris Instance UUID [PSARC/2010/226 FastTrack timeout 06/25/2010] In-reply-to: <20100620222732.GA12378@xanadu.sfbay.sun.com> To: Dan Price Cc: Cynthia McGuire , PSARC-record@sac.sfbay.sun.com, psarc-ext@sun.com, fma-core@sun.com Message-id: <4C1F0F98.4000802@oracle.com> Organization: Oracle Corporation MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 X-Source-IP: acsmt353.oracle.com [141.146.40.153] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A090202.4C1F0FA7.00DB:SCFMA4539814,ss=1,fgs=0 References: <201006190152.o5J1qlg3020977@sac.sfbay.sun.com> <20100620222732.GA12378@xanadu.sfbay.sun.com> User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.1.9) Gecko/20100524 Lightning/1.0b1 Thunderbird/3.0.4 Status: RO Content-Length: 2575 On 06/21/10 08:27 AM, Dan Price wrote: > On Fri 18 Jun 2010 at 06:52PM, Cynthia McGuire wrote: >> >> Template Version: @(#)sac_nextcase 1.70 03/30/10 SMI >> This information is Copyright (c) 2010, Oracle and/or its affiliates. All rights reserved. >> 1. Introduction >> 1.1. Project/Component Working Name: >> Solaris Instance UUID >> 1.2. Name of Document Author/Supplier: >> Author: Gavin Maltby >> 1.3 Date of This Document: >> 18 June, 2010 >> 4. Technical Description >> See the case directory for more detail > > This case might be easier to grok if it was called "crash dump UUID" > or "boot UUID" or some such-- "image UUID" seems vague, and this case > doesn't appear to be generating anything which is scoped beyond the use > case of crash dumps and live dumps (which seems perfectly reasonable). I'm mostly interested in crash dumps, so I don't mind renaming it as such. There are times in service when it is valuable to ask a customer to collect a bunch of info while the problem is experienced, which might or might not included a forced crash dump or live savecore. For those purposes it can be useful to have label under which such information can go, and that is what the instance uuid can provide. In cases where there have been a few reboots/crashes it can be a real mess trying to correlate which observations came from where. > I presume when you say "UUID" you are stating that the UUID will comply > with some particular standard? RFC 4122? Yes; thought I remembered adding that but it may be to a related FMA portfolio. > My big question, thought, is "Why log it to syslog?" The case provides > no rationale for this and seems to tempt customers to consume it-- > especially as it marks the log message itself as "committed", which > seemed surprising to me. There may be other committed syslog messages > but I don't know of them, and it seems like this would be something > to avoid (i.e. log messages are not an interface). I have no need to log it to syslog for the immediate use in mind. I figured that for the kind of service data collection scenarios mentioned above that a record of the instance UUID would be useful. When you're performing some post-mortem panic analysis it can be useful to correlate messages with the particular panic. So I think that logging it has it uses. I made it Committed because its unlikely ever to have to evolve, and anyone trawling it out of messages files can rely on its structure. I was being generous there - I don't mind dropping the stability level. Thanks Gavin From sacadmin Sun Jul 4 18:01:44 2010 Received: from dm-sfbay-02.sfbay.sun.com (dm-sfbay-02.SFBay.Sun.COM [129.146.11.31]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id o6511iAe025082; Sun, 4 Jul 2010 18:01:44 -0700 (PDT) Received: from brmea-mail-4.sun.com (brmea-mail-4.Sun.COM [192.18.98.36]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id o6511iAT009250; Sun, 4 Jul 2010 18:01:44 -0700 (PDT) Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id o6511hLt029328; Mon, 5 Jul 2010 01:01:43 GMT Received: from acsmt353.oracle.com (acsmt353.oracle.com [141.146.40.153]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o64L571h008418; Mon, 5 Jul 2010 01:01:43 GMT Received: from abhmt010.oracle.com by acsmt353.oracle.com with ESMTP id 396344731278291685; Sun, 04 Jul 2010 18:01:25 -0700 Received: from tara.local (/10.7.250.215) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Sun, 04 Jul 2010 18:01:24 -0700 Message-ID: <4C313040.9000509@oracle.com> Date: Sun, 04 Jul 2010 18:07:12 -0700 From: Cynthia McGuire User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228) MIME-Version: 1.0 To: Cynthia McGuire CC: PSARC-record@sac.sfbay.sun.com, psarc-ext@sun.com, fma-core@sun.com Subject: Re: Solaris Instance UUID [PSARC/2010/226 FastTrack timeout 06/25/2010] References: <201006190152.o5J1qlg3020977@sac.sfbay.sun.com> In-Reply-To: <201006190152.o5J1qlg3020977@sac.sfbay.sun.com> Content-Type: multipart/mixed; boundary="------------020205090405030401020704" X-Source-IP: acsmt353.oracle.com [141.146.40.153] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A090209.4C312EF7.00CA:SCFMA4539814,ss=1,fgs=0 Status: RO Content-Length: 5700 This is a multi-part message in MIME format. --------------020205090405030401020704 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Gavin has updated the case, see attached and the case directory. There do not appear to be any other outstanding issues. Cindi Cynthia McGuire wrote: > Template Version: @(#)sac_nextcase 1.70 03/30/10 SMI > This information is Copyright (c) 2010, Oracle and/or its affiliates. All rights reserved. > 1. Introduction > 1.1. Project/Component Working Name: > Solaris Instance UUID > 1.2. Name of Document Author/Supplier: > Author: Gavin Maltby > 1.3 Date of This Document: > 18 June, 2010 > 4. Technical Description > See the case directory for more detail > > 6. Resources and Schedule > 6.4. Steering Committee requested information > 6.4.1. Consolidation C-team Name: > ON > 6.5. ARC review type: FastTrack > 6.6. ARC Exposure: open > -- Cynthia McGuire, Fishworks http://blogs.sun.com/cindi --------------020205090405030401020704 Content-Type: text/plain; name="fasttrack.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="fasttrack.txt" 1. Introduction 1.1. Project/Component Working Name: Solaris Instance UUID 1.2. Name of Document Author/Supplier: Gavin Maltby 1.3. Date of This Document: 05/19/2010 1.5. Email Aliases: 1.5.1. Responsible Manager: gavin.gibson@oracle.com 1.5.2. Responsible Engineer: gavin.maltby@oracle.com 4. Technical Description: 4.1. Details: 4.1.1 Summary We associate a unique identifier with each running Solaris instance. An "instance" in this sense is a boot of Solaris, so the intention is to identify each distinct boot of a Solaris installation from the next (*). The instance identifier will serve to identify a running Solaris instance and correlate it with any crash dump images thereof (both "live savecore" images and panics). The identifier takes the form of a 36-character UUID string which is generated during boot (at the time that we appoint any dump device, but still generated even if there is no dump device) and embedded in the running kernel image. This is a once-only operation - further attempts to set the image UUID will fail with EALREADY. All interfaces are Private - see 4.5. We arc them, nevertheless, to document them for various crashdump analysis tools. This feature does not overlap with that of FWARC/2009/680 - the UUID there identifies distinct ldoms, not Solaris images. (*) In some virtualization products it is possible that a booted instance is snapshotted and that snapshot restored to a running state repeatedly. In this case the instance UUID will not change at each snapshot resume - it will be that of the original boot before snapshot. In this case a single image UUID can be associated with multiple panics. 4.1.2 Setting Image UUID An undocumented (private) option -i to dumpadm is used to set the current instance UUID during boot. This is executed during the start method script for service instance system/filesystem/usr:default which is the earliest point in boot that a dump device can be appointed (for zfs root filesystems). If something should cause this method script to run again then the repeated attempted to set a UUID will fail harmlessly. Similarly a command line use of dumpadm -i will fail if filesystem/usr has already come online. 4.1.3 Retrieving Image UUID The current image UUID may be retrieved from userland through a (private) ioctl DIOCGETUUID on /dev/dump; you need suitable permissions to open /dev/dump even for reading. In a crashdump image it is retrievable both from the dump header and from the kernel variable dump_osimage_uuid. Within the kernel, the UUID of the image may be retrieved with dump_get_uuid(). We do not deliver a command line utility to query the current image UUID. 4.1.4 Image UUID in syslog When it is first generated, the instance UUID is noted in the messages file (but not to the console): May 31 22:57:55 parity genunix: [ID 227219 kern.info] This Solaris instance has UUID 18081944-4691-639f-e2cf-8f2054a0ded4 4.1.5 Image UUID in mdb The image UUID is displayed by ::status in mdb in both live and post-mortem kernel debug sessions. # mdb -k > ::status debugging live kernel (64-bit) on parity operating system: 5.11 swfma-bld (i86pc) image uuid: 18081944-4691-639f-e2cf-8f2054a0ded4 If we panic that instance and run mdb on the resulting crashdump: # mdb -k 0 > ::status debugging crash dump vmcore.0 (64-bit) from parity operating system: 5.11 snv_138 (i86pc) image uuid: 18081944-4691-639f-e2cf-8f2054a0ded4 panic message: forced crash dump initiated at user request dump content: kernel pages only 4.1.6 DUMP_VERSION and PANICBUFVERS Changes The DUMP_VERSION used in a struct dumphdr (written at the head and tail of a crashdump) is bumped from 9 to 10; version 10 includes a character array dump_uuid. The PANICBUFVERS, which describes the format of panic data captured in panicbuf and written out to a crash dump, is bumped from 1 to 2. 4.5. Interfaces: Interface Stability ----------------------- ------------ dump_get_uuid Consolidation Private dump_set_uuid Project Private dumpadm -i Project Private DIOCSETUUID Project Private DIOCGETUUID Project Private dump_osimage_uuid Project Private panicdata pd_uuid Consolidation Private UUID syslog message Not An Interface 4.6. Doc Impact: 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open --------------020205090405030401020704-- From cynthia.mcguire@oracle.com Sun Jul 4 18:01:45 2010 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id o6511jvw025086 for ; Sun, 4 Jul 2010 18:01:45 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.4) with ESMTP id o6511ixc064943; Sun, 4 Jul 2010 19:01:45 -0600 (MDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0L5200J0B86WIS00@brm-avmta-1.central.sun.com>; Sun, 04 Jul 2010 19:01:44 -0600 (MDT) Received: from brmea-mail-4.sun.com ([192.18.98.36]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0L52000DX86WS2B0@brm-avmta-1.central.sun.com>; Sun, 04 Jul 2010 19:01:44 -0600 (MDT) Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id o6511hLt029328; Mon, 05 Jul 2010 01:01:43 +0000 (GMT) Received: from acsmt353.oracle.com (acsmt353.oracle.com [141.146.40.153]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o64L571h008418; Mon, 05 Jul 2010 01:01:43 +0000 (GMT) Received: from abhmt010.oracle.com by acsmt353.oracle.com with ESMTP id 396344731278291685; Sun, 04 Jul 2010 18:01:25 -0700 Received: from tara.local (/10.7.250.215) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Sun, 04 Jul 2010 18:01:24 -0700 Date: Sun, 04 Jul 2010 18:07:12 -0700 From: Cynthia McGuire Subject: Re: Solaris Instance UUID [PSARC/2010/226 FastTrack timeout 06/25/2010] In-reply-to: <201006190152.o5J1qlg3020977@sac.sfbay.sun.com> To: Cynthia McGuire Cc: PSARC-record@sac.sfbay.sun.com, psarc-ext@sun.com, fma-core@sun.com Message-id: <4C313040.9000509@oracle.com> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_0yixGl7iDn6eOIkEB9Pd3g)" X-PMX-Version: 5.4.1.325704 X-Source-IP: acsmt353.oracle.com [141.146.40.153] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A090209.4C312EF7.00CA:SCFMA4539814,ss=1,fgs=0 References: <201006190152.o5J1qlg3020977@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228) Status: RO Content-Length: 5695 This is a multi-part message in MIME format. --Boundary_(ID_0yixGl7iDn6eOIkEB9Pd3g) Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT Gavin has updated the case, see attached and the case directory. There do not appear to be any other outstanding issues. Cindi Cynthia McGuire wrote: > Template Version: @(#)sac_nextcase 1.70 03/30/10 SMI > This information is Copyright (c) 2010, Oracle and/or its affiliates. All rights reserved. > 1. Introduction > 1.1. Project/Component Working Name: > Solaris Instance UUID > 1.2. Name of Document Author/Supplier: > Author: Gavin Maltby > 1.3 Date of This Document: > 18 June, 2010 > 4. Technical Description > See the case directory for more detail > > 6. Resources and Schedule > 6.4. Steering Committee requested information > 6.4.1. Consolidation C-team Name: > ON > 6.5. ARC review type: FastTrack > 6.6. ARC Exposure: open > -- Cynthia McGuire, Fishworks http://blogs.sun.com/cindi --Boundary_(ID_0yixGl7iDn6eOIkEB9Pd3g) Content-type: text/plain; name=fasttrack.txt Content-transfer-encoding: 7BIT Content-disposition: inline; filename=fasttrack.txt 1. Introduction 1.1. Project/Component Working Name: Solaris Instance UUID 1.2. Name of Document Author/Supplier: Gavin Maltby 1.3. Date of This Document: 05/19/2010 1.5. Email Aliases: 1.5.1. Responsible Manager: gavin.gibson@oracle.com 1.5.2. Responsible Engineer: gavin.maltby@oracle.com 4. Technical Description: 4.1. Details: 4.1.1 Summary We associate a unique identifier with each running Solaris instance. An "instance" in this sense is a boot of Solaris, so the intention is to identify each distinct boot of a Solaris installation from the next (*). The instance identifier will serve to identify a running Solaris instance and correlate it with any crash dump images thereof (both "live savecore" images and panics). The identifier takes the form of a 36-character UUID string which is generated during boot (at the time that we appoint any dump device, but still generated even if there is no dump device) and embedded in the running kernel image. This is a once-only operation - further attempts to set the image UUID will fail with EALREADY. All interfaces are Private - see 4.5. We arc them, nevertheless, to document them for various crashdump analysis tools. This feature does not overlap with that of FWARC/2009/680 - the UUID there identifies distinct ldoms, not Solaris images. (*) In some virtualization products it is possible that a booted instance is snapshotted and that snapshot restored to a running state repeatedly. In this case the instance UUID will not change at each snapshot resume - it will be that of the original boot before snapshot. In this case a single image UUID can be associated with multiple panics. 4.1.2 Setting Image UUID An undocumented (private) option -i to dumpadm is used to set the current instance UUID during boot. This is executed during the start method script for service instance system/filesystem/usr:default which is the earliest point in boot that a dump device can be appointed (for zfs root filesystems). If something should cause this method script to run again then the repeated attempted to set a UUID will fail harmlessly. Similarly a command line use of dumpadm -i will fail if filesystem/usr has already come online. 4.1.3 Retrieving Image UUID The current image UUID may be retrieved from userland through a (private) ioctl DIOCGETUUID on /dev/dump; you need suitable permissions to open /dev/dump even for reading. In a crashdump image it is retrievable both from the dump header and from the kernel variable dump_osimage_uuid. Within the kernel, the UUID of the image may be retrieved with dump_get_uuid(). We do not deliver a command line utility to query the current image UUID. 4.1.4 Image UUID in syslog When it is first generated, the instance UUID is noted in the messages file (but not to the console): May 31 22:57:55 parity genunix: [ID 227219 kern.info] This Solaris instance has UUID 18081944-4691-639f-e2cf-8f2054a0ded4 4.1.5 Image UUID in mdb The image UUID is displayed by ::status in mdb in both live and post-mortem kernel debug sessions. # mdb -k > ::status debugging live kernel (64-bit) on parity operating system: 5.11 swfma-bld (i86pc) image uuid: 18081944-4691-639f-e2cf-8f2054a0ded4 If we panic that instance and run mdb on the resulting crashdump: # mdb -k 0 > ::status debugging crash dump vmcore.0 (64-bit) from parity operating system: 5.11 snv_138 (i86pc) image uuid: 18081944-4691-639f-e2cf-8f2054a0ded4 panic message: forced crash dump initiated at user request dump content: kernel pages only 4.1.6 DUMP_VERSION and PANICBUFVERS Changes The DUMP_VERSION used in a struct dumphdr (written at the head and tail of a crashdump) is bumped from 9 to 10; version 10 includes a character array dump_uuid. The PANICBUFVERS, which describes the format of panic data captured in panicbuf and written out to a crash dump, is bumped from 1 to 2. 4.5. Interfaces: Interface Stability ----------------------- ------------ dump_get_uuid Consolidation Private dump_set_uuid Project Private dumpadm -i Project Private DIOCSETUUID Project Private DIOCGETUUID Project Private dump_osimage_uuid Project Private panicdata pd_uuid Consolidation Private UUID syslog message Not An Interface 4.6. Doc Impact: 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open --Boundary_(ID_0yixGl7iDn6eOIkEB9Pd3g)--