From tl41329@sac.sfbay.sun.com Thu Jul 17 18:58:00 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m6I1vxTd001933 for ; Thu, 17 Jul 2008 18:58:00 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m6I1vtSW009825; Fri, 18 Jul 2008 09:57:58 +0800 (SGT) 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 <0K4600C07ISL5U00@nwk-avmta-2.sfbay.sun.com>; Thu, 17 Jul 2008 18:57:57 -0700 (PDT) Received: from dm-sfbay-01.sfbay.sun.com ([129.145.155.118]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K46005LJISKG970@nwk-avmta-2.sfbay.sun.com>; Thu, 17 Jul 2008 18:57:56 -0700 (PDT) Received: from sac.sfbay.sun.com (new-sac.SFBay.Sun.COM [129.146.175.65]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m6I1vu2e055052; Thu, 17 Jul 2008 18:57:56 -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 m6I1vs7l001928; Thu, 17 Jul 2008 18:57:54 -0700 (PDT) Received: (from tl41329@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id m6I1vsS8001924; Thu, 17 Jul 2008 18:57:54 -0700 (PDT) Date: Thu, 17 Jul 2008 18:57:54 -0700 (PDT) From: Tzongyu Paul Lee Subject: RaidCfg GUID and volume activation support [PSARC/2008/458 FastTrack timeout 07/24/2008] To: PSARC-ext@sun.com Message-id: <200807180157.m6I1vsS8001924@sac.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 8549 I am sponsoring this fast-track for Jie Cao. Requested release binding is minor, and the timer is set to 07/24/2008. Regards, T.Paul Lee --------------- Template Version: @(#)sac_nextcase 1.66 04/17/08 SMI This information is Copyright 2008 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: RaidCfg GUID and volume activation support 1.2. Name of Document Author/Supplier: Author: Jie Cao 1.3 Date of This Document: 17 July, 2008 4. Technical Description 1. Introduction 1.1. Project/Component Working Name: RaidCfg GUID and volume activation support 1.2. Name of Document Author/Supplier: Author: jie.cao@sun.com 1.3 Date of This Document: Jul 7th, 2008 4. Technical Description 4.1 Summary The raidctl utility is a RAID configuration tool for mpt controllers in Solaris; however, it needs to be enhanced when the mpt-mpxio feature is enabled. The reason is that the mpt controller can only deal with the target id with RAID management commands; but accessible disks are represented using GUID when mpt-mpxio is enabled. Considering that there's no 1-1 mapping method between the GUID and target id, raidctl should provide the GUID information so that user can figure out the disk target id. Meanwhile, for mpt controllers, volume can be in an inactive state and in this case no RAID config action can be conducted. The raidctl utility needs to be enhanced to detect volume inactive status and to include volume activation capability. 4.2 Proposal The GUID is a property for a physical disk. Presently raidctl utility can display detailed information for a physical disk, including the target id, but not GUID info. The solution is to add the GUID information to the disk information output so user can determine both the target id and GUID for a given disk; thus the user can use the corresponding target id for further RAID management actions. Accordingly, a new Property object (to hold GUID information) will be introduced into the RaidCfg software. Each Property object will only associate with a single disk object as a component and its attribute is defined as follows: typedef struct { uint32_t prop_id; uint32_t prop_size; property_type_t prop_type; char prop[1]; } property_attr_t; prop_id: A unique id number within a controller. It's used to address the property object. prop_size: Length of buffer specified by the 'prop' field. prop_type: Specifying what kind of information in buffer 'prop'. Currently can only be PROP_GUID. prop: Buffer used to store property information. The GUID information is generated by physical disk devices so each layer of RaidCfg software will include some adjustment to meet this requirement. All interfaces including CLI, API and SPI will be enhanced with backward compatibilities, to provide features to address the property objects and to query the corresponding attributes. And for the volume activation issue, a new flag will be introduced into the 'state' field of array object attribute (see section 3.2.3 in RaidCfg design doc version 1.1 [1]) to represent the array's activating status. When bit 31 of the 'state' field is 1, the volume is in inactive state. Bit 16 to bit 30 are reserved. Bit 0 to bit 15 remains unchanged. The API function raidcfg_set_attr() and SPI function rdcfg_set_attr() will be enhanced to provide volume-activation feature. 4.3 Interface Summary RaidCfg CLI interface: Remains as Evolving. GUID information output had been added to disk information display in a compatible format. And for a given volume, if it's in inactive state, array information display output will show this status. See accompanied diff file for the raidctl manpage. RaidCfg API interface: Remains as project-private. The following API routines will be enhanced with backward compatibility: (1) int raidcfg_get_type(int obj_handle) Constant OBJ_TYPE_PROP had been added to return value range; (2) int raidcfg_list_head(int obj_handle, raid_obj_type_id_t type) Constant OBJ_TYPE_PROP had been added to value range of parameter 'type'. (3) int raidcfg_get_attr(int obj_handle, void *attr) This function will be enhanced with the capability to query attributes for a Property object (presently only for GUID information). In this case 'attr' must point to a structure of type raidcfg_prop_t, defined as follows: typedef property_attr_t raidcfg_prop_t; Note that if 'prop_size' filed is 0, this function will fill this field with required length of buffer 'prop' to store the property information (hereby the GUID, as a string); otherwise 'prop' will be filled with the property information. (4) int raidcfg_set_attr(int obj_handle, uint32_t set_cmd, void *value, char **err_str) This function will be enhanced with the capability to activate a volume. In this case 'obj_handle' should contain the array object handle, 'set_cmd' should be SET_ACTIVATION_PLY and 'value' should point to a value of ARRAY_ACT_ACTIVATE. RaidCfg SPI interface: Remains as project-private. The following SPI routines will be enhanced with backward compatibility: (1) int rdcfg_compnum(uint32_t controller_id, uint32_t container_id, raid_obj_type_id_t container_type, raid_obj_type_id_t component_type) A new combination of parameters of 'container_type' and 'component_type' will be added, as follows: container_type component_type ====================================================== RAID_OBJ_TYPE_DISK RAID_OBJ_TYPE_PROP This combination will be used to query for the number of Property object for a given disk. (2) int rdcfg_complist(uint32_t controller_id, uint32_t container_id, raid_obj_type_id_t container_type, raid_obj_type_id_t comp_type, int comp_num, uint32_t *ids) A new combination of parameters of 'container_type' and 'component_type' is added, as follows: container_type component_type ====================================================== RAID_OBJ_TYPE_DISK RAID_OBJ_TYPE_PROP This combination will be used to query for Property object ids for a given disk. (3) int rdcfg_get_attr(uint32_t controller_id, uint32_t device_id, uint32_t index_id, raid_obj_type_id_t type, void *attr) A new combination of parameters of 'type', 'device_id' and 'index_id' will be added, as follows: type device_id index_id ======================================================== RAID_OBJ_TYPE_PROP disk_id prop_id Buffer pointed by 'attr' will contain a structure of type 'property_attr_t', which is defined as follows: typedef struct { uint32_t prop_id; uint32_t prop_size; property_type_t prop_type; char prop[1]; } property_attr_t; Since presently the Property object can only hold the GUID information, rdcfg_get_attr() should always fill 'prop_type' with constant PROP_GUID; and 'prop_size' stands for the length of 'prop'. If 'prop_size' is 0, rdcfg_get_attr() should fill it with length of the GUID information (in bytes) and return SUCCESS; otherwise rdcfg_get_attr() should put the GUID information into buffer 'prop' and return SUCCESS. (4) int rdcfg_set_attr(uint32_t controller_id, uint32_t device_id, uint32_t cmd, uint32_t *value, char **err_ptr) A new combination of parameters of 'device_id', 'cmd' and 'value' will be added, as follows: device_id cmd *value ============================================================= array_id SET_ACTIVATION_PLY ARRAY_ACT_ACTIVATE This combination will be used to activate the volume in question. 4.4 References [1] PSARC/2005/204 RaidCfg project [2] PSARC/2006/663 RaidCfg MPT adjustment [3] PSARC/2007/667 RaidCfg disk_id adjustment [4] Manpage of raidctl(1M) 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 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 James.McPherson@sun.com Thu Jul 17 19:09:54 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m6I29rZu002068 for ; Thu, 17 Jul 2008 19:09:53 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m6I293We002455 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Fri, 18 Jul 2008 03:09:52 +0100 (BST) 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 <0K4600101JCEP700@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 17 Jul 2008 19:09:50 -0700 (PDT) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K4600LBUJCAHG70@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 17 Jul 2008 19:09:47 -0700 (PDT) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m6I2AE9L022342 for ; Fri, 18 Jul 2008 02:10:14 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0K4600H01J9QAQ00@mail-apac.sun.com> (original mail from James.McPherson@Sun.COM) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 18 Jul 2008 10:09:15 +0800 (SGT) Received: from [192.168.1.10] ([220.157.71.44]) by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0K4600M9GJBC9VYY@mail-apac.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 18 Jul 2008 10:09:15 +0800 (SGT) Date: Fri, 18 Jul 2008 12:09:49 +1000 From: "James C. McPherson" Subject: Re: RaidCfg GUID and volume activation support [PSARC/2008/458 FastTrack timeout 07/24/2008] In-reply-to: <200807180157.m6I1vsS8001924@sac.sfbay.sun.com> Sender: James.McPherson@sun.com To: Jerend Cao Cc: Paul Lee , PSARC-ext@sun.com Reply-to: James.McPherson@sun.com Message-id: <487FFB6D.2050200@Sun.COM> Organization: Sun Microsystems MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=UTF-8 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200807180157.m6I1vsS8001924@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.14 (X11/20080616) Status: RO Content-Length: 334 Hi Jerend, will this fasttrack address the issues in 6523832 raidctl cannot support mpxio-capable disks when mpxio enabled on the hba controller. and 6544176 raidctl manpage needs updating thankyou, James -- Senior Kernel Software Engineer, Solaris Sun Microsystems http://blogs.sun.com/jmcp http://www.jmcp.homeunix.com/blog From Jie.Cao@sun.com Thu Jul 17 20:06:58 2008 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 m6I36wED002805 for ; Thu, 17 Jul 2008 20:06:58 -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.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m6I36w1Y023961 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Thu, 17 Jul 2008 20:06:58 -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 <0K4600F03LZML600@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 17 Jul 2008 20:06:58 -0700 (PDT) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K46005C0LZLG0B0@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 17 Jul 2008 20:06:58 -0700 (PDT) Received: from fe-apac-06.sun.com (fe-apac-06.sun.com [192.18.19.177] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m6I385V1005468 for ; Fri, 18 Jul 2008 03:08:05 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0K4600001LUHSS00@mail-apac.sun.com> (original mail from Jie.Cao@Sun.COM) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 18 Jul 2008 11:04:37 +0800 (SGT) Received: from [129.158.218.193] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0K460097FLVO8AP4@mail-apac.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 18 Jul 2008 11:04:37 +0800 (SGT) Date: Fri, 18 Jul 2008 11:07:12 +0800 From: jie cao - Sun Microsystems - Beijing China Subject: Re: RaidCfg GUID and volume activation support [PSARC/2008/458 FastTrack timeout 07/24/2008] In-reply-to: <487FFB6D.2050200@Sun.COM> Sender: Jie.Cao@sun.com To: James.McPherson@sun.com Cc: Paul Lee , PSARC-ext@sun.com Message-id: <488008E0.6050401@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=UTF-8 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200807180157.m6I1vsS8001924@sac.sfbay.sun.com> <487FFB6D.2050200@Sun.COM> User-Agent: Thunderbird 2.0.0.14 (X11/20080519) Status: RO Content-Length: 1012 No, 2008/458 is for the following: 6523832 raidctl cannot support mpxio-capable disks when mpxio enabled on the hba controller. 6695619 raidctl should allow activation of RAID volumes BTW, this psarc case will be open to the community, and it's based on the previous 3 cases. How's the status of making the previous 3 RaidCfg cases open to community? I remember you sent out the request email, but I haven't got any further feedback... Regards, Jerend James C. McPherson wrote: > > Hi Jerend, > will this fasttrack address the issues in > > > 6523832 raidctl cannot support mpxio-capable disks when mpxio enabled > on the hba controller. > > and > > 6544176 raidctl manpage needs updating > > > thankyou, > James > -- > Senior Kernel Software Engineer, Solaris > Sun Microsystems > http://blogs.sun.com/jmcp http://www.jmcp.homeunix.com/blog From Tzongyu.Lee@sun.com Wed Jul 23 11:54:27 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m6NIsQL1004324 for ; Wed, 23 Jul 2008 11:54:27 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m6NIsO0M021656 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 23 Jul 2008 19:54:26 +0100 (BST) 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 <0K4H0090736OJ100@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 23 Jul 2008 11:54:24 -0700 (PDT) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K4H008ZX36M6630@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 23 Jul 2008 11:54:23 -0700 (PDT) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m6NItWsk026078 for ; Wed, 23 Jul 2008 18:55:32 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0K4H00E0132MQ000@mail-apac.sun.com> (original mail from Tzongyu.Lee@Sun.COM) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 24 Jul 2008 02:53:50 +0800 (SGT) Received: from [129.158.148.46] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0K4H00LRL35OOO70@mail-apac.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 24 Jul 2008 02:53:50 +0800 (SGT) Date: Thu, 24 Jul 2008 02:54:02 +0800 From: Tzongyu Paul Lee Subject: approved in 7/23 meeting [Re: RaidCfg GUID and volume activation support [PSARC/2008/458 FastTrack timeout 07/24/2008]] In-reply-to: <200807180157.m6I1vsS8001924@sac.sfbay.sun.com> Sender: Tzongyu.Lee@sun.com To: PSARC-ext@sun.com Cc: Jie Jerend Cao Reply-to: Tzongyu.Lee@sun.com Message-id: <48877E4A.5090700@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200807180157.m6I1vsS8001924@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.12 (X11/20080228) Status: RO Content-Length: 9264 This fasttrack 2008/458 was approved in the 7/23 Open Meeting. Regards, Paul ------ Tzongyu Paul Lee wrote: > I am sponsoring this fast-track for Jie Cao. > Requested release binding is minor, and the timer is set to > 07/24/2008. > > Regards, > T.Paul Lee > --------------- > > Template Version: @(#)sac_nextcase 1.66 04/17/08 SMI > This information is Copyright 2008 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > RaidCfg GUID and volume activation support > 1.2. Name of Document Author/Supplier: > Author: Jie Cao > 1.3 Date of This Document: > 17 July, 2008 > 4. Technical Description > 1. Introduction > 1.1. Project/Component Working Name: > RaidCfg GUID and volume activation support > 1.2. Name of Document Author/Supplier: > Author: jie.cao@sun.com > 1.3 Date of This Document: > Jul 7th, 2008 > 4. Technical Description > > 4.1 Summary > > The raidctl utility is a RAID configuration tool for mpt controllers in > Solaris; however, it needs to be enhanced when the mpt-mpxio feature is > enabled. The reason is that the mpt controller can only deal with the > target id with RAID management commands; but accessible disks are > represented using GUID when mpt-mpxio is enabled. Considering that there's > no 1-1 mapping method between the GUID and target id, raidctl should > provide the GUID information so that user can figure out the disk target > id. > > Meanwhile, for mpt controllers, volume can be in an inactive state > and in this case no RAID config action can be conducted. The raidctl > utility needs to be enhanced to detect volume inactive status > and to include volume activation capability. > > 4.2 Proposal > > The GUID is a property for a physical disk. Presently raidctl utility can > display detailed information for a physical disk, including the target > id, but not GUID info. The solution is to add the GUID information to the > disk information output so user can determine both the target id and > GUID for a given disk; thus the user can use the corresponding target id for further > RAID management actions. > > Accordingly, a new Property object (to hold GUID > information) will be introduced into the RaidCfg software. Each Property > object will only associate with a single disk object as a component and > its attribute is defined as follows: > > typedef struct { > uint32_t prop_id; > uint32_t prop_size; > property_type_t prop_type; > char prop[1]; > } property_attr_t; > > prop_id: A unique id number within a controller. It's used to address > the property object. > prop_size: Length of buffer specified by the 'prop' field. > prop_type: Specifying what kind of information in buffer 'prop'. > Currently can only be PROP_GUID. > prop: Buffer used to store property information. > > The GUID information is generated by physical disk devices so each layer > of RaidCfg software will include some adjustment to meet this requirement. > All interfaces including CLI, API and SPI will be enhanced with backward > compatibilities, to provide features to address the property objects and > to query the corresponding attributes. > > And for the volume activation issue, a new flag will be introduced into > the 'state' field of array object attribute (see section 3.2.3 in RaidCfg > design doc version 1.1 [1]) to represent the array's activating status. When > bit 31 of the 'state' field is 1, the volume is in inactive state. Bit > 16 to bit 30 are reserved. Bit 0 to bit 15 remains unchanged. > > The API function raidcfg_set_attr() and SPI function rdcfg_set_attr() > will be enhanced to provide volume-activation feature. > > > 4.3 Interface Summary > > RaidCfg CLI interface: > Remains as Evolving. > GUID information output had been added to disk information display > in a compatible format. And for a given volume, if it's in inactive > state, array information display output will show this status. See > accompanied diff file for the raidctl manpage. > > RaidCfg API interface: > Remains as project-private. > The following API routines will be enhanced with backward compatibility: > > (1) int raidcfg_get_type(int obj_handle) > Constant OBJ_TYPE_PROP had been added to return value range; > > (2) int raidcfg_list_head(int obj_handle, raid_obj_type_id_t type) > Constant OBJ_TYPE_PROP had been added to value range of > parameter 'type'. > > (3) int raidcfg_get_attr(int obj_handle, void *attr) > This function will be enhanced with the capability to query > attributes for a Property object (presently only for GUID > information). In this case 'attr' must point to a structure of > type raidcfg_prop_t, defined as follows: > > typedef property_attr_t raidcfg_prop_t; > > Note that if 'prop_size' filed is 0, this function will fill > this field with required length of buffer 'prop' to store the > property information (hereby the GUID, as a string); otherwise > 'prop' will be filled with the property information. > > (4) int raidcfg_set_attr(int obj_handle, uint32_t set_cmd, > void *value, char **err_str) > This function will be enhanced with the capability to activate > a volume. In this case 'obj_handle' should contain the array > object handle, 'set_cmd' should be SET_ACTIVATION_PLY and > 'value' should point to a value of ARRAY_ACT_ACTIVATE. > > > RaidCfg SPI interface: > Remains as project-private. > The following SPI routines will be enhanced with backward compatibility: > > (1) int rdcfg_compnum(uint32_t controller_id, uint32_t container_id, > raid_obj_type_id_t container_type, raid_obj_type_id_t > component_type) > A new combination of parameters of 'container_type' and > 'component_type' will be added, as follows: > > container_type component_type > ====================================================== > RAID_OBJ_TYPE_DISK RAID_OBJ_TYPE_PROP > > This combination will be used to query for the number of > Property object for a given disk. > > (2) int rdcfg_complist(uint32_t controller_id, uint32_t container_id, > raid_obj_type_id_t container_type, raid_obj_type_id_t comp_type, > int comp_num, uint32_t *ids) > A new combination of parameters of 'container_type' and > 'component_type' is added, as follows: > > container_type component_type > ====================================================== > RAID_OBJ_TYPE_DISK RAID_OBJ_TYPE_PROP > > This combination will be used to query for Property object ids > for a given disk. > > (3) int rdcfg_get_attr(uint32_t controller_id, uint32_t device_id, > uint32_t index_id, raid_obj_type_id_t type, void *attr) > A new combination of parameters of 'type', 'device_id' and > 'index_id' will be added, as follows: > > type device_id index_id > ======================================================== > RAID_OBJ_TYPE_PROP disk_id prop_id > > Buffer pointed by 'attr' will contain a structure of type > 'property_attr_t', which is defined as follows: > > typedef struct { > uint32_t prop_id; > uint32_t prop_size; > property_type_t prop_type; > char prop[1]; > } property_attr_t; > > Since presently the Property object can only hold the GUID > information, rdcfg_get_attr() should always fill 'prop_type' > with constant PROP_GUID; and 'prop_size' stands for the length > of 'prop'. If 'prop_size' is 0, rdcfg_get_attr() should fill > it with length of the GUID information (in bytes) and return > SUCCESS; otherwise rdcfg_get_attr() should put the GUID > information into buffer 'prop' and return SUCCESS. > > (4) int rdcfg_set_attr(uint32_t controller_id, uint32_t device_id, > uint32_t cmd, uint32_t *value, char **err_ptr) > A new combination of parameters of 'device_id', 'cmd' and > 'value' will be added, as follows: > > device_id cmd *value > ============================================================= > array_id SET_ACTIVATION_PLY ARRAY_ACT_ACTIVATE > > This combination will be used to activate the volume in question. > > > 4.4 References > > [1] PSARC/2005/204 RaidCfg project > > > [2] PSARC/2006/663 RaidCfg MPT adjustment > > > [3] PSARC/2007/667 RaidCfg disk_id adjustment > > > [4] Manpage of raidctl(1M) > > > 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 > > 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 > > -- Tzongyu Paul Lee, Tzongyu.Lee@Sun.Com or Paul.Lee@Sun.COM BJS05 7225, x84343 http://blogs.sun.com/tpaullee/ Feel the Pulses of China http://tpaullee.blogspot.com/ - use google reader in China From Tzongyu.Lee@sun.com Thu Sep 25 02:50:07 2008 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 m8P9o7De017725 for ; Thu, 25 Sep 2008 02:50:07 -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.2) with ESMTP id m8P9o558025994 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Thu, 25 Sep 2008 03:50:06 -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 <0K7Q00F1ZWNH6E00@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 25 Sep 2008 03:50:05 -0600 (MDT) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K7Q00LRCWNGBG90@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 25 Sep 2008 03:50:05 -0600 (MDT) Received: from fe-apac-06.sun.com (fe-apac-06.sun.com [192.18.19.177] (may be forged)) by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m8P9o3pM002417 for ; Thu, 25 Sep 2008 09:50:03 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0K7Q00401WMVC300@mail-apac.sun.com> (original mail from Tzongyu.Lee@Sun.COM) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 25 Sep 2008 17:50:03 +0800 (SGT) Received: from [129.158.218.85] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0K7Q003PDWNELJM0@mail-apac.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 25 Sep 2008 17:50:03 +0800 (SGT) Date: Thu, 25 Sep 2008 17:48:02 +0800 From: Tzongyu Paul Lee Subject: Re: approved in 7/23 meeting [Re: RaidCfg GUID and volume activation support [PSARC/2008/458 FastTrack timeout 07/24/2008]] In-reply-to: <48877E4A.5090700@Sun.COM> Sender: Tzongyu.Lee@sun.com To: PSARC-ext@sun.com Cc: Jie Jerend Cao , "Yubo, Ryan Wang" Reply-to: Tzongyu.Lee@sun.com Message-id: <48DB5E52.40501@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=UTF-8 Content-transfer-encoding: 8BIT X-PMX-Version: 5.4.1.325704 References: <200807180157.m6I1vsS8001924@sac.sfbay.sun.com> <48877E4A.5090700@Sun.COM> User-Agent: Thunderbird 2.0.0.4 (X11/20070723) Status: RO Content-Length: 9520 Hi all concerned, This case was introduced to add GUID and volume activation support for the mpt-mpxio feature in July 2008. This code is going in to S10U7 in November time frame. However, it turns out that the Vela product needs this to be patch-supported for the S10U6+patch customers. And I would like to request the change of this case from *minor* binding release to *patch* binding release in order for this to go into the S10U7 sustaining/patch gate. Would be happy to answer any question and/or concerns on this request. If I don't hear anything in a couple of days, I would go ahead to revise the case file with a note on this change. Thanks for your attention, T.Paul Tzongyu Paul Lee 写道: > This fasttrack 2008/458 was approved in the 7/23 Open Meeting. > > Regards, > Paul > ------ > > Tzongyu Paul Lee wrote: >> I am sponsoring this fast-track for Jie Cao. >> Requested release binding is minor, and the timer is set to >> 07/24/2008. >> >> Regards, >> T.Paul Lee >> --------------- >> >> Template Version: @(#)sac_nextcase 1.66 04/17/08 SMI >> This information is Copyright 2008 Sun Microsystems >> 1. Introduction >> 1.1. Project/Component Working Name: >> RaidCfg GUID and volume activation support >> 1.2. Name of Document Author/Supplier: >> Author: Jie Cao >> 1.3 Date of This Document: >> 17 July, 2008 >> 4. Technical Description >> 1. Introduction >> 1.1. Project/Component Working Name: >> RaidCfg GUID and volume activation support >> 1.2. Name of Document Author/Supplier: >> Author: jie.cao@sun.com >> 1.3 Date of This Document: >> Jul 7th, 2008 >> 4. Technical Description >> >> 4.1 Summary >> >> The raidctl utility is a RAID configuration tool for mpt controllers in >> Solaris; however, it needs to be enhanced when the mpt-mpxio feature is >> enabled. The reason is that the mpt controller can only deal with the >> target id with RAID management commands; but accessible disks are >> represented using GUID when mpt-mpxio is enabled. Considering that >> there's >> no 1-1 mapping method between the GUID and target id, raidctl should >> provide the GUID information so that user can figure out the disk target >> id. >> >> Meanwhile, for mpt controllers, volume can be in an inactive state >> and in this case no RAID config action can be conducted. The raidctl >> utility needs to be enhanced to detect volume inactive status >> and to include volume activation capability. >> >> 4.2 Proposal >> >> The GUID is a property for a physical disk. Presently raidctl utility >> can >> display detailed information for a physical disk, including the target >> id, but not GUID info. The solution is to add the GUID information to >> the >> disk information output so user can determine both the target id and >> GUID for a given disk; thus the user can use the corresponding target >> id for further >> RAID management actions. >> >> Accordingly, a new Property object (to hold GUID >> information) will be introduced into the RaidCfg software. Each Property >> object will only associate with a single disk object as a component and >> its attribute is defined as follows: >> >> typedef struct { >> uint32_t prop_id; >> uint32_t prop_size; >> property_type_t prop_type; >> char prop[1]; >> } property_attr_t; >> >> prop_id: A unique id number within a controller. It's used to address >> the property object. >> prop_size: Length of buffer specified by the 'prop' field. >> prop_type: Specifying what kind of information in buffer 'prop'. >> Currently can only be PROP_GUID. >> prop: Buffer used to store property information. >> >> The GUID information is generated by physical disk devices so each layer >> of RaidCfg software will include some adjustment to meet this >> requirement. >> All interfaces including CLI, API and SPI will be enhanced with backward >> compatibilities, to provide features to address the property objects and >> to query the corresponding attributes. >> >> And for the volume activation issue, a new flag will be introduced into >> the 'state' field of array object attribute (see section 3.2.3 in >> RaidCfg >> design doc version 1.1 [1]) to represent the array's activating >> status. When >> bit 31 of the 'state' field is 1, the volume is in inactive state. Bit >> 16 to bit 30 are reserved. Bit 0 to bit 15 remains unchanged. >> >> The API function raidcfg_set_attr() and SPI function rdcfg_set_attr() >> will be enhanced to provide volume-activation feature. >> >> >> 4.3 Interface Summary >> >> RaidCfg CLI interface: >> Remains as Evolving. >> GUID information output had been added to disk information display >> in a compatible format. And for a given volume, if it's in inactive >> state, array information display output will show this status. See >> accompanied diff file for the raidctl manpage. >> >> RaidCfg API interface: >> Remains as project-private. >> The following API routines will be enhanced with backward compatibility: >> >> (1) int raidcfg_get_type(int obj_handle) >> Constant OBJ_TYPE_PROP had been added to return value range; >> >> (2) int raidcfg_list_head(int obj_handle, raid_obj_type_id_t type) >> Constant OBJ_TYPE_PROP had been added to value range of >> parameter 'type'. >> >> (3) int raidcfg_get_attr(int obj_handle, void *attr) >> This function will be enhanced with the capability to query >> attributes for a Property object (presently only for GUID >> information). In this case 'attr' must point to a structure of >> type raidcfg_prop_t, defined as follows: >> >> typedef property_attr_t raidcfg_prop_t; >> >> Note that if 'prop_size' filed is 0, this function will fill >> this field with required length of buffer 'prop' to store the >> property information (hereby the GUID, as a string); otherwise >> 'prop' will be filled with the property information. >> >> (4) int raidcfg_set_attr(int obj_handle, uint32_t set_cmd, >> void *value, char **err_str) >> This function will be enhanced with the capability to activate >> a volume. In this case 'obj_handle' should contain the array >> object handle, 'set_cmd' should be SET_ACTIVATION_PLY and >> 'value' should point to a value of ARRAY_ACT_ACTIVATE. >> >> >> RaidCfg SPI interface: >> Remains as project-private. >> The following SPI routines will be enhanced with backward compatibility: >> >> (1) int rdcfg_compnum(uint32_t controller_id, uint32_t container_id, >> raid_obj_type_id_t container_type, raid_obj_type_id_t >> component_type) >> A new combination of parameters of 'container_type' and >> 'component_type' will be added, as follows: >> >> container_type component_type >> ====================================================== >> RAID_OBJ_TYPE_DISK RAID_OBJ_TYPE_PROP >> >> This combination will be used to query for the number of >> Property object for a given disk. >> >> (2) int rdcfg_complist(uint32_t controller_id, uint32_t container_id, >> raid_obj_type_id_t container_type, raid_obj_type_id_t comp_type, >> int comp_num, uint32_t *ids) >> A new combination of parameters of 'container_type' and >> 'component_type' is added, as follows: >> >> container_type component_type >> ====================================================== >> RAID_OBJ_TYPE_DISK RAID_OBJ_TYPE_PROP >> >> This combination will be used to query for Property object ids >> for a given disk. >> >> (3) int rdcfg_get_attr(uint32_t controller_id, uint32_t device_id, >> uint32_t index_id, raid_obj_type_id_t type, void *attr) >> A new combination of parameters of 'type', 'device_id' and >> 'index_id' will be added, as follows: >> >> type device_id index_id >> ======================================================== >> RAID_OBJ_TYPE_PROP disk_id prop_id >> >> Buffer pointed by 'attr' will contain a structure of type >> 'property_attr_t', which is defined as follows: >> >> typedef struct { >> uint32_t prop_id; >> uint32_t prop_size; >> property_type_t prop_type; >> char prop[1]; >> } property_attr_t; >> >> Since presently the Property object can only hold the GUID >> information, rdcfg_get_attr() should always fill 'prop_type' >> with constant PROP_GUID; and 'prop_size' stands for the length >> of 'prop'. If 'prop_size' is 0, rdcfg_get_attr() should fill >> it with length of the GUID information (in bytes) and return >> SUCCESS; otherwise rdcfg_get_attr() should put the GUID >> information into buffer 'prop' and return SUCCESS. >> >> (4) int rdcfg_set_attr(uint32_t controller_id, uint32_t device_id, >> uint32_t cmd, uint32_t *value, char **err_ptr) >> A new combination of parameters of 'device_id', 'cmd' and 'value' >> will be added, as follows: >> >> device_id cmd *value >> ============================================================= >> array_id SET_ACTIVATION_PLY ARRAY_ACT_ACTIVATE >> >> This combination will be used to activate the volume in question. >> >> >> 4.4 References >> >> [1] PSARC/2005/204 RaidCfg project >> >> >> [2] PSARC/2006/663 RaidCfg MPT adjustment >> >> >> [3] PSARC/2007/667 RaidCfg disk_id adjustment >> >> >> [4] Manpage of raidctl(1M) >> >> >> 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 >> >> 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 >> > -- Tzongyu Paul Lee, Tzongyu.Lee@Sun.Com or Paul.Lee@Sun.COM BJS05 7225, x84343 From carlsonj@phorcys.east.sun.com Thu Sep 25 05:11:28 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m8PCBRAU023290 for ; Thu, 25 Sep 2008 05:11:28 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m8PCBPMI007197; Thu, 25 Sep 2008 20:11:26 +0800 (SGT) 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 <0K7R0020H370MB00@brm-avmta-1.central.sun.com>; Thu, 25 Sep 2008 06:11:24 -0600 (MDT) Received: from phorcys.east.sun.com ([129.148.174.143]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K7R000W3370KT20@brm-avmta-1.central.sun.com>; Thu, 25 Sep 2008 06:11:24 -0600 (MDT) Received: from phorcys.east.sun.com (localhost [127.0.0.1]) by phorcys.east.sun.com (8.14.3+Sun/8.14.3) with ESMTP id m8PCBOk9020415; Thu, 25 Sep 2008 08:11:24 -0400 (EDT) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.3+Sun/8.14.3/Submit) id m8PCBNKa020412; Thu, 25 Sep 2008 08:11:23 -0400 (EDT) Date: Thu, 25 Sep 2008 08:11:23 -0400 From: James Carlson Subject: Re: approved in 7/23 meeting [Re: RaidCfg GUID and volume activation support [PSARC/2008/458 FastTrack timeout 07/24/2008]] In-reply-to: <48DB5E52.40501@Sun.COM> To: Tzongyu.Lee@sun.com Cc: PSARC-ext@sun.com, Jie Jerend Cao , "Yubo, Ryan Wang" Message-id: <18651.32747.974163.425806@gargle.gargle.HOWL> MIME-version: 1.0 X-Mailer: VM 7.01 under Emacs 21.3.1 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200807180157.m6I1vsS8001924@sac.sfbay.sun.com> <48877E4A.5090700@Sun.COM> <48DB5E52.40501@Sun.COM> Status: RO Content-Length: 708 Tzongyu Paul Lee writes: > Would be happy to answer any question and/or concerns on this request. > If I don't hear anything in a couple of days, I would go ahead to revise > the case file > with a note on this change. The original case talked about an "accompanying" raidctl man page, but as far as I can tell, none was submitted. Could you please detail the changes to raidctl? In particular, what part of the output is changing, and is there anything dependent on that output? -- James Carlson, Solaris Networking Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 From Ryan.Wang@Sun.COM Thu Sep 25 18:46:45 2008 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 m8Q1kjwV015473 for ; Thu, 25 Sep 2008 18:46:45 -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.2) with ESMTP id m8Q1khdh020863 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Thu, 25 Sep 2008 19:46:44 -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 <0K7S008034XVC600@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Thu, 25 Sep 2008 18:46:43 -0700 (PDT) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K7S002JL4XTY730@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Thu, 25 Sep 2008 18:46:42 -0700 (PDT) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m8Q1kexB000966 for ; Fri, 26 Sep 2008 01:46:40 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0K7S008014XEDK00@mail-apac.sun.com> (original mail from Ryan.Wang@Sun.COM) for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Fri, 26 Sep 2008 09:46:40 +0800 (SGT) Received: from [129.158.218.37] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0K7S003U04XRJP5R@mail-apac.sun.com> for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Fri, 26 Sep 2008 09:46:40 +0800 (SGT) Date: Fri, 26 Sep 2008 09:45:00 +0800 From: Yu-Bo Ryan Wang Subject: Re: approved in 7/23 meeting [Re: RaidCfg GUID and volume activation support [PSARC/2008/458 FastTrack timeout 07/24/2008]] In-reply-to: <18651.32747.974163.425806@gargle.gargle.HOWL> Sender: Ryan.Wang@Sun.COM To: James Carlson Cc: Tzongyu.Lee@Sun.COM, PSARC-ext@Sun.COM, Jie Jerend Cao Message-id: <48DC3E9C.7040305@Sun.COM> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_oJ9cXXPpWkA41thosLjESw)" X-PMX-Version: 5.4.1.325704 References: <200807180157.m6I1vsS8001924@sac.sfbay.sun.com> <48877E4A.5090700@Sun.COM> <48DB5E52.40501@Sun.COM> <18651.32747.974163.425806@gargle.gargle.HOWL> User-Agent: Thunderbird 2.0.0.14 (X11/20080728) Status: RO Content-Length: 28715 This is a multi-part message in MIME format. --Boundary_(ID_oJ9cXXPpWkA41thosLjESw) Content-type: multipart/alternative; boundary="Boundary_(ID_3lCi6tz8yGbNNZFvockyZw)" --Boundary_(ID_3lCi6tz8yGbNNZFvockyZw) Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT Hi James, The latest raidctl man page and diff file from the previous one has been attached, and it has been integrated into nv_98. For the output change, as the section 4.3 mentioned, GUID information output had been added to disk information display in a compatible format. And for a given volume, if it's in inactive state, array information display output will show this status. See accompanied diff file for the raidctl manpage. Currently, there is nothing dependent on that output. Thanks, Ryan James Carlson wrote: > Tzongyu Paul Lee writes: > >> Would be happy to answer any question and/or concerns on this request. >> If I don't hear anything in a couple of days, I would go ahead to revise >> the case file >> with a note on this change. >> > > The original case talked about an "accompanying" raidctl man page, but > as far as I can tell, none was submitted. > > Could you please detail the changes to raidctl? In particular, what > part of the output is changing, and is there anything dependent on > that output? > > -- Regards, WANG, Yu-Bo Ryan SUN Microsystems China --Boundary_(ID_3lCi6tz8yGbNNZFvockyZw) Content-type: text/html; charset=ISO-8859-1 Content-transfer-encoding: 7BIT Hi James,

The latest raidctl man page and diff file from the previous one has been attached, and it has been integrated into nv_98.

For the output change, as the section 4.3  mentioned, 
        GUID information output had been added to disk information display
	in a compatible format. And for a given volume, if it's in inactive
        state, array information display output will show this status. See
	accompanied diff file for the raidctl manpage.

Currently, there is nothing dependent on that output.

Thanks,
Ryan


James Carlson wrote: 
Tzongyu Paul Lee writes:
  
Would be happy to answer any question and/or concerns on this request.
If I don't hear anything in a couple of days, I would go ahead to revise 
the case file
with a note on this change.
    

The original case talked about an "accompanying" raidctl man page, but
as far as I can tell, none was submitted.

Could you please detail the changes to raidctl?  In particular, what
part of the output is changing, and is there anything dependent on
that output?

  

-- 
Regards,

WANG, Yu-Bo Ryan
 
SUN Microsystems China
--Boundary_(ID_3lCi6tz8yGbNNZFvockyZw)-- --Boundary_(ID_oJ9cXXPpWkA41thosLjESw) Content-type: text/plain; name=raidctl.diff.txt Content-transfer-encoding: 7BIT Content-disposition: inline; filename=raidctl.diff.txt 291,294c291,297 < Change the property value for a given RAID volume. < Currently, only the cache write policy is changeable < ("on" or "off"). So param can only be the string "wp" < (SET_WR_POLICY), and value can be either "on" or "off". --- > Change the property value for a given RAID volume. > This option can be used to change cache write policy or > to activate a volume. When changing the cache write > policy, param should be the string "wp" (SET_WR_POLICY), > and value can be either "on" or "off"; and when used to > to activate a volume, param should be "state" and value > should be "activate". 371a375 > Firmware 372a377,379 > Displays the firmware version of the disk. > > 386a394 > GUID 387a396,398 > GUID string for the specified disk. This is an addi- > tional information and might be in-available in some > cases. 392d402 < 432,438c442,449 < Displays the status of the specified volume, or the < sub-volumes/disks that form the specified volume. < For a volume, the status can be "OPTIMAL" (operating < optimally), "DEGRADED" (operating with reduced func- < tionality), "FAILED" (non-functional), or "SYNC" < (disks are syncing). For a disk, the status can be < "GOOD", "FAILED", or "MISSING". --- > Displays the status of the specified volume, or the > sub-volumes / disks that form the specified volume. > For an in-active volume, the status should be > "INACTIVE"; otherwise it can be "OPTIMAL" (operating > optimally), "DEGRADED" (operating with reduced func- > tionality), "FAILED" (non-functional), or "SYNC" > (disks are syncing). For a disk, the status can > be "GOOD", "FAILED", or "MISSING". 695a707,708 > The following command displays information about disk 0.0.0 > on controller 0: 696a710 > # raidctl -l -g 0.0.0 0 698,699c712,715 < The following command displays information about disk 0.3.0 < on controller 2: --- > Disk Vendor Product Firmware Capacity Status HSP > ---------------------------------------------------------------------------- > 0.0.0 HITACHI H101473SCSUN72G SQ02 68.3G GOOD N/A > GUID:2000000cca02536c 701,708d716 < # raidctl -l -g 0.3.0 2 < < Disk Vendor Product Capacity Status HSP < -------------------------------------------------------------- < 0.3.0 MAXTOR ATLAS10K4_36SC 34732M GOOD c2t0d0 < < < 804c812 < # raidctl -a set -p "wp=off" c0t0d0 --- > # raidctl -p "wp=off" c0t0d0 806a815,820 > The following command activates the volume of c1t0d0: > > > # raidctl -p "state=activate" c1t0d0 > > --Boundary_(ID_oJ9cXXPpWkA41thosLjESw) Content-type: text/plain; name=raidctl.txt Content-transfer-encoding: 7BIT Content-disposition: inline; filename=raidctl.txt System Administration Commands raidctl(1M) NAME raidctl - RAID hardware utility SYNOPSIS raidctl -C "disks" [-r raid_level] [-z capacity] [-s stripe_size] [-f] controller raidctl -d [-f] volume raidctl -F filename [-f] controller... raidctl -a {set | unset} -g disk {volume | controller} raidctl -p "param=value" [-f] volume raidctl -c [-f] [-r raid_level] disk1 disk2 [disk3...] raidctl -l -g disk controller raidctl -l volume raidctl -l controller... raidctl [-l] raidctl -S [volume | controller] raidctl -S -g disk controller raidctl -h DESCRIPTION The raidctl utility is a hardware RAID configuration tool that supports different RAID controllers by providing a CLI (command-line interface) to end-users to create, delete or display RAID volume(s). The utility can also used to set properties of a volume, assign hot-spare (HSP) disks to volumes or controllers, and to update firmware/fcode/BIOS for RAID controllers. SunOS 5.11 Last change: 24 Jul 2008 1 System Administration Commands raidctl(1M) The raidctl utility requires privileges that are controlled by the underlying file-system permissions. Only privileged users can manipulate the RAID system configuration. If a non-privileged user attempts to run raidctl, the command fails with an exit status of 1. The raidctl utility, as described in this man page, defines a broad set of command line options to provide management for full-featured RAID controllers. However, support for a given option depends on two elements: o the presence of a software driver o the firmware level of the RAID device The dependency on a software driver is due to the design of raidctl. The utility is built on a common library that enables the insertion of plug-in modules for different drivers. Currently, the Solaris operating system is shipped with a plug-in for the mpt driver. This plug-in does not support all of the raidctl options. On a given storage dev- ice, options might be further limited by the device's firmware level. The level of support for the various raidctl options cannot be determined by raidctl. The user must rely on the documen- tation for his RAID controller or hardware platform. Currently, raidctl Currently, raidctl provides some level of support for the following RAID controllers: o LSI1020 SCSI HBA o LSI1030 SCSI HBA o LSI1064 SAS HBA o LSI1068 SAS HBA All of the above HBAs are maintained by the mpt driver, on X86-32/64 and SPARC platforms. OPTIONS The following options are supported: -C "disks" [-r raid_level] [-z capacity] [-s stripe_size] [-f] controller SunOS 5.11 Last change: 24 Jul 2008 2 System Administration Commands raidctl(1M) Create a RAID volume using specified disks. When creating a RAID volume using this option, the iden- tity of the newly created volume is automatically gen- erated and raidctl reports it to the user. The argument specified by this option contains the ele- ments used to form the volume that will be created. Ele- ments can be either disks or sub-volumes, where disks are separated by space(s) and a sub-volume is a set of disks grouped by parenthesis. All disks should be in C.ID.L expression (for example, 0.1.2 represents a phy- sical disk of channel 0, target id 1, and logical unit number 2). The argument must match the RAID level speci- fied by the -r option, even if it's omitted. This means the argument can only be: for RAID 0 At least 2 disks for RAID 1 Only 2 disks for RAID 1E At least 3 disks for RAID 5 At least 3 disks for RAID 10 At least 2 sub-volumes, each sub-volume must be formed by 2 disks for RAID 50 At least 2 sub-volumes, each sub-volume must be formed by at least 3 disks, and the disk amount in each sub-volume should be the same For example, the expression "0.0.0 0.1.0" means that the 2 specified disks form a RAID volume, which can either be a RAID 0 or a RAID 1 volume. "(0.0.0 0.1.0)(0.2.0 SunOS 5.11 Last change: 24 Jul 2008 3 System Administration Commands raidctl(1M) 0.3.0)" means that the first 2 disks and the last 2 disks form 2 sub-volumes, and that these 2 sub-volumes form a RAID 10 volume. See the EXAMPLES section for more samples. The -r option specifies the RAID level of the volume that will be created. Possible levels are 0, 1, 1E, 5, 10, 50. If this option is omitted, raidctl creates a RAID 1 volume by default. The -z option specifies the capacity of the volume that will be created. The unit can be tera-bytes, giga-bytes, or mega-bytes (for example, 2t, 10g, 20m, and so on). If this option is omitted, raidctl calculates the maximum capacity of the volume that can be created by the speci- fied disks and uses this value to create the volume. The -s option specifies the stripe size of the volume that will be created. The possible values are 512, 1k, 2k, 4k, 8k, 16k, 32k, 64k, or 128k. If this option is omitted, raidctl chooses an appropriate value for the volume (for example, 64k). In some cases, the creation of a RAID volume may cause data on specified disks to be lost (for instance, on LSI1020, LSI1030, SAS1064, or SAS1068 HBAs), and raidctl prompts the user for confirmation about the creation. Use the -f option to force the volume creation without prompting the user for confirmation. The controller argument is used to identify which RAID controller the specified disks belongs. The -l option can be used to list the controller's ID number. -d [-f] volume Delete the RAID volume specified as volume. The volume is specified in canonical form (for example, c0t0d0). When a volume is deleted, all data is lost. Therefore, unless the -f option is specified, raidctl prompts the user for confirmation before deleting the volume. When a RAID 1 volume is deleted from a LSI1020, LSI1030, SAS1064, or SAS1068 HBA, the primary and secondary disks are "split". If the volume was in SYNCING state, the primary will contain the data, and the secondary will not. If the volume state was OPTIMAL, both disks will contain a complete image of the data. SunOS 5.11 Last change: 24 Jul 2008 4 System Administration Commands raidctl(1M) -F filename [-f] controller... Update the firmware running on the specified controller(s). The raidctl utility prompts the user for confirmation of this action, unless the -f option is provided. -a {set | unset} -g disk {volume | controller} If the volume is specified, raidctl sets or unsets the disk as a local hot-spare disk dedicated to the volume, depending on the value specified by the -a option. If the controller is specified, raidctl sets or unsets the disk as a global hot-spare disk. -p "param=value" [-f] volume Change the property value for a given RAID volume. This option can be used to change cache write policy or to activate a volume. When changing the cache write policy, param should be the string "wp" (SET_WR_POLICY), and value can be either "on" or "off"; and when used to to activate a volume, param should be "state" and value should be "activate". Changing a RAID volume's property may affect the inter- nal behavior of the RAID controller, so raidctl prompts the user for a confirmation before applying the change, unless the -f option is specified. -c [-f] [-r raid_level] disk1 disk2 [disk3...] Create a volume using the specified disks. This is an alternative to the -C option with similar functionality. This option is preserved for compatibility reasons, but only works with LSI1020, LSI1030, SAS1064, and SAS1068 HBAs to create RAID 0, RAID 1, or RAID 1E volumes. For other HBAs, the user can only use the -C option. The -r option can be used to specify the RAID level of the target volume. If the -r option is omitted, raidctl will create a RAID 1 volume. Disks must be specified in Solaris canonical format (for example, c0t0d0). Creating a RAID 1 volume with this option replaces the contents of disk2 with the contents of disk1. When the user creates a RAID volume with this option, the RAID volume assumes the identity of disk1. Other disks become invisible and the RAID volume appears as SunOS 5.11 Last change: 24 Jul 2008 5 System Administration Commands raidctl(1M) one disk. Creating a volume with this option is by default interactive. The user must answer a prompt affirmatively to create the volume. Use the -f option to force the volume creation without prompting the user for confirma- tion. -l -g disk controller Display information about the specified disk of the given controller. The output includes the following information: Disk Displays the disk in C.ID.L expression disk. Vendor Displays the vendor ID string. Product Displays the product ID string. Capacity Displays the total capacity of the disk. Firmware Displays the firmware version of the disk. Status Displays the current status of disk. The status can be either "GOOD" (operating normally), "FAILED" (non-functional), or "MISSING" (disk not present). HSP Indicates if the disk has been set as a global hot- spare disk, local hot-spare disk, or a normal one. If it is a local hot-spare disk, all volumes which this disk is assigned to are displayed. GUID GUID string for the specified disk. This is an addi- tional information and might be in-available in some cases. SunOS 5.11 Last change: 24 Jul 2008 6 System Administration Commands raidctl(1M) -l volume Display information about the specified volume. The out- put includes the following information: Volume Displays volume in canonical format. Sub Displays sub-volumes, if the specified volume is of RAID 10 or RAID 50 volume. Disk Displays all disks that form the specified volume. Stripe Size Displays the stripe size of the volume. Status Displays the status of the specified volume, or the sub-volumes / disks that form the specified volume. For an in-active volume, the status should be "INACTIVE"; otherwise it can be "OPTIMAL" (operating optimally), "DEGRADED" (operating with reduced func- tionality), "FAILED" (non-functional), or "SYNC" (disks are syncing). For a disk, the status can be "GOOD", "FAILED", or "MISSING". Cache Indicates whether the cache is applied to I/O write activities. The cache can be either "ON" or "OFF". RAID level Displays the RAID level. The RAID level can be either 0, 1, 1E, 5, 10, or 50. -l controller ... SunOS 5.11 Last change: 24 Jul 2008 7 System Administration Commands raidctl(1M) Display information about the specified controller(s). The output includes the following information: Controller Displays the RAID controller's ID number. Type Displays the RAID controller's product type. fw_version Displays the controller's firmware version. [-l] List all RAID related objects that the raidctl utility can manipulate, including all available RAID controll- ers, RAID volumes, and physical disks. The -l option can be omitted. The output includes the following information: Controller Displays the RAID controller's ID number. Volume Displays the logical RAID volume name. Disk Displays the RAID disk in C.ID.L expression. -S [volume | controller] Takes a snapshot of the RAID configuration information including all available RAID devices, RAID controllers, volumes, and disks. Each line of the output specifies a RAID device and its related information, separated by space(s). All volumes SunOS 5.11 Last change: 24 Jul 2008 8 System Administration Commands raidctl(1M) and disks belong to the last specified controller. The output lists the following information: Controller Displays the controller ID number, and the con- troller type string in double-quotation marks. Volume Displays the RAID volume name, number of component disks, the C.ID.L expression of the component disks, the RAID level, and the status. The status can be either OPTIMAL, DEGRADED, FAILED, or SYNCING. Disk Displays the C.ID.L expression of the disk, and the status. The status can be either GOOD, FAILED, or HSP (disk has been set as a stand-by disk). If a volume or a controller is specified, a snapshot is only taken of the information for the specified volume or controller. -S -g disk controller Takes a snapshot of the information for the specified disk. -h Print out the usage string. EXAMPLES Example 1 Creating the RAID Configuration The following command creates a RAID 0 volume of 10G on con- troller 0, and the stripe size will be set to 64k: # raidctl -C "0.0.0 0.2.0" -r 0 -z 10g -s 64k 0 SunOS 5.11 Last change: 24 Jul 2008 9 System Administration Commands raidctl(1M) The following command creates a RAID 1 volume on controller 2: # raidctl -C "0.0.0 1.1.0" -r 1 2 The following command creates a RAID 5 volume on controller 2: # raidctl -C "0.0.0 0.1.0 0.2.0" -r 5 2 The following command creates a RAID 10 volume on controller 0: # raidctl -C "(0.0.0 0.1.0)(0.2.0 0.3.0)" -r 10 0 The following command creates a RAID 50 volume on controller 0: # raidctl -C "(0.0.0 0.1.0 0.2.0)(0.3.0 0.4.0 0.5.0)" -r 50 0 Example 2 Displaying the RAID Configuration The following command displays all available controllers, volumes, and disks: # raidctl -l Controller: 0 Controller: 2 Volume:c2t0d0 Disk: 0.0.0 Disk: 0.1.0 Disk: 0.2.0 Disk: 0.3.0(HSP) SunOS 5.11 Last change: 24 Jul 2008 10 System Administration Commands raidctl(1M) The following command displays information about controller 2: # raidctl -l 2 Controller Type Fw_version -------------------------------------------------------------- c2 LSI 1030 1.03.39.00 The following command displays information about the speci- fied volume: # raidctl -l c2t0d0 Volume Size Stripe Status Cache RAID Sub Size Level Disk -------------------------------------------------------------- c2t0d0 10240M 64K OPTIMAL ON RAID5 0.0.0 5120M GOOD 0.1.0 5120M GOOD 0.2.0 5120M GOOD The following command displays information about disk 0.0.0 on controller 0: # raidctl -l -g 0.0.0 0 Disk Vendor Product Firmware Capacity Status HSP ---------------------------------------------------------------------------- 0.0.0 HITACHI H101473SCSUN72G SQ02 68.3G GOOD N/A GUID:2000000cca02536c Example 3 Deleting the RAID Configuration The following command deletes a volume: # raidctl -d c0t0d0 SunOS 5.11 Last change: 24 Jul 2008 11 System Administration Commands raidctl(1M) Example 4 Updating Flash Images on the Controller The following command updates flash images on the controller 0: # raidctl -F lsi_image.fw 0 Example 5 Setting or unsetting a hot-spare disk The following command sets disk 0.3.0 on controller 2 as a global hot-spare disk: # raidctl -a set -g 0.3.0 2 The following command sets disk 0.3.0 on controller 2 as a local hot-spare disk to volume c2t0d0: # raidctl -a set -g 0.3.0 c2t0d0 The following command converts disk 0.3.0 on controller 2 from a global hot-spare disk to a normal one: # raidctl -a unset -g 0.3.0 2 The following command removes disk 0.3.0 from being a local hot-spare disk from volume c2t0d0: # raidctl -a unset -g 0.3.0 c2t0d0 Example 6 Setting the volume's property SunOS 5.11 Last change: 24 Jul 2008 12 System Administration Commands raidctl(1M) The following command sets the write policy of the volume to "off": # raidctl -p "wp=off" c0t0d0 The following command activates the volume of c1t0d0: # raidctl -p "state=activate" c1t0d0 Example 7 Creating volumes with the -c option The following command creates a RAID 1 volume: # raidctl -c c0t0d0 c0t1d0 The following command creates a RAID 0 volume: # raidctl -c -r 0 c0t1d0 c0t2d0 c0t3d0 Example 8 Taking a snapshot of the RAID configuration infor- mation The following command takes a snapshot of all RAID devices: # # raidctl -S 1 "LSI 1030" c1t1d0 2 0.2.0 0.3.0 1 DEGRADED 0.2.0 GOOD 0.3.0 FAILED The following command takes a snapshot about volume c1t0d0: # raidctl -S c1t0d0 c1t0d0 2 0.0.0 0.1.0 1 OPTIMAL SunOS 5.11 Last change: 24 Jul 2008 13 System Administration Commands raidctl(1M) The following command takes a snapshot about disk 0.1.0 on controller 1: # raidctl -S -g 0.1.0 1 0.1.0 GOOD EXIT STATUS The following exit values are returned: 0 Successful completion. 1 Invalid command line input or permission denied. 2 Request operation failed. ATTRIBUTES See attributes(5) for descriptions of the following attri- butes: ____________________________________________________________ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | |_____________________________|_____________________________| | Availability | SUNWcsu | |_____________________________|_____________________________| | Interface Stability | Evolving | |_____________________________|_____________________________| SEE ALSO attributes(5), mpt(7D) System Administration Guide: Basic Administration WARNINGS Do not create raid volumes on internal SAS disks if you are going to use the Solaris Multipathing I/O feature (also SunOS 5.11 Last change: 24 Jul 2008 14 System Administration Commands raidctl(1M) known as MPxIO). Creating a new raid volume under Solaris Multipathing will give your root device a new GUID which does not match the GUID for the existing devices. This will cause a boot failure since your root device entry in /etc/vfstab will not match. NOTES The -z option is not supported on systems that use the mpt driver and LSI RAID controllers. SunOS 5.11 Last change: 24 Jul 2008 15 --Boundary_(ID_oJ9cXXPpWkA41thosLjESw)-- From Tzongyu.Lee@sun.com Thu Sep 25 19:54:14 2008 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 m8Q2sEG9016558 for ; Thu, 25 Sep 2008 19:54:14 -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.2) with ESMTP id m8Q2sDQu039588 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Thu, 25 Sep 2008 20:54:14 -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 <0K7S00G0182BB600@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Thu, 25 Sep 2008 19:54:11 -0700 (PDT) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K7S00295829Y290@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Thu, 25 Sep 2008 19:54:10 -0700 (PDT) Received: from fe-apac-06.sun.com (fe-apac-06.sun.com [192.18.19.177] (may be forged)) by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m8Q2s9b0005304 for ; Fri, 26 Sep 2008 02:54:09 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0K7S00I018103C00@mail-apac.sun.com> (original mail from Tzongyu.Lee@Sun.COM) for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Fri, 26 Sep 2008 10:54:09 +0800 (SGT) Received: from [129.158.218.85] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0K7S00CKI8232X40@mail-apac.sun.com> for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Fri, 26 Sep 2008 10:54:05 +0800 (SGT) Date: Fri, 26 Sep 2008 10:52:03 +0800 From: Tzongyu Paul Lee Subject: Re: approved in 7/23 meeting [Re: RaidCfg GUID and volume activation support [PSARC/2008/458 FastTrack timeout 07/24/2008]] In-reply-to: <48DC3E9C.7040305@Sun.COM> Sender: Tzongyu.Lee@sun.com To: Yu-Bo Ryan Wang Cc: James Carlson , PSARC-ext@sun.com, Jie Jerend Cao Reply-to: Tzongyu.Lee@sun.com Message-id: <48DC4E53.6020601@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=UTF-8 Content-transfer-encoding: 8BIT X-PMX-Version: 5.4.1.325704 References: <200807180157.m6I1vsS8001924@sac.sfbay.sun.com> <48877E4A.5090700@Sun.COM> <48DB5E52.40501@Sun.COM> <18651.32747.974163.425806@gargle.gargle.HOWL> <48DC3E9C.7040305@Sun.COM> User-Agent: Thunderbird 2.0.0.4 (X11/20070723) Status: RO Content-Length: 1394 Captured now in http://sac.sfbay.sun.com/Archives/CaseLog/arc/PSARC/2008/458/ Paul ------- Yu-Bo Ryan Wang 写道: > Hi James, > > The latest raidctl man page and diff file from the previous one has > been attached, and it has been integrated into nv_98. > > For the output change, as the section 4.3 mentioned, > GUID information output had been added to disk information display > in a compatible format. And for a given volume, if it's in inactive > state, array information display output will show this status. See > accompanied diff file for the raidctl manpage. > > Currently, there is nothing dependent on that output. > > > Thanks, > Ryan > > > James Carlson wrote: >> Tzongyu Paul Lee writes: >> >>> Would be happy to answer any question and/or concerns on this request. >>> If I don't hear anything in a couple of days, I would go ahead to revise >>> the case file >>> with a note on this change. >>> >> >> The original case talked about an "accompanying" raidctl man page, but >> as far as I can tell, none was submitted. >> >> Could you please detail the changes to raidctl? In particular, what >> part of the output is changing, and is there anything dependent on >> that output? >> >> > > -- > Regards, > > WANG, Yu-Bo Ryan > > SUN Microsystems China > -- Tzongyu Paul Lee, Tzongyu.Lee@Sun.Com or Paul.Lee@Sun.COM BJS05 7225, x84343 From carlsonj@phorcys.east.sun.com Fri Sep 26 04:53:01 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m8QBr0Sk000374 for ; Fri, 26 Sep 2008 04:53:00 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m8QBqqi5008938; Fri, 26 Sep 2008 19:52:58 +0800 (SGT) 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 <0K7S00E03X09S800@brm-avmta-1.central.sun.com>; Fri, 26 Sep 2008 05:52:57 -0600 (MDT) Received: from phorcys.east.sun.com ([129.148.174.143]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K7S000PBX08PSB0@brm-avmta-1.central.sun.com>; Fri, 26 Sep 2008 05:52:56 -0600 (MDT) Received: from phorcys.east.sun.com (localhost [127.0.0.1]) by phorcys.east.sun.com (8.14.3+Sun/8.14.3) with ESMTP id m8QBquRL011249; Fri, 26 Sep 2008 07:52:56 -0400 (EDT) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.3+Sun/8.14.3/Submit) id m8QBquap011246; Fri, 26 Sep 2008 07:52:56 -0400 (EDT) Date: Fri, 26 Sep 2008 07:52:56 -0400 From: James Carlson Subject: Re: approved in 7/23 meeting [Re: RaidCfg GUID and volume activation support [PSARC/2008/458 FastTrack timeout 07/24/2008]] In-reply-to: <48DC3E9C.7040305@Sun.COM> To: Yu-Bo Ryan Wang Cc: Tzongyu.Lee@sun.com, PSARC-ext@sun.com, Jie Jerend Cao Message-id: <18652.52504.463746.851318@gargle.gargle.HOWL> MIME-version: 1.0 X-Mailer: VM 7.01 under Emacs 21.3.1 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200807180157.m6I1vsS8001924@sac.sfbay.sun.com> <48877E4A.5090700@Sun.COM> <48DB5E52.40501@Sun.COM> <18651.32747.974163.425806@gargle.gargle.HOWL> <48DC3E9C.7040305@Sun.COM> Status: RO Content-Length: 1276 Yu-Bo Ryan Wang writes: > For the output change, as the section 4.3 mentioned, > > GUID information output had been added to disk information display > in a compatible format. And for a given volume, if it's in inactive > state, array information display output will show this status. See > accompanied diff file for the raidctl manpage. > > Currently, there is nothing dependent on that output. I'm a little surprised that adding a field in the middle of a table is considered a "compatible format," particularly so in a patch, but if we're absolutely sure that there's nothing dependent on this but human eyeballs, then it seems ok to me. Please do make sure that when the man page is updated, the stability is updated to the current terminology (what was once "Evolving" is now "Committed"), and that the man page makes clear that the stability applies to the command line arguments only, as the output from this command (as this project makes plain) is substantially less than "Committed." It's probably "Volatile" at best. -- James Carlson, Solaris Networking Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 From Ryan.Wang@Sun.COM Sat Sep 27 02:22:53 2008 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 m8R9MrVV007772 for ; Sat, 27 Sep 2008 02:22:53 -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.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m8R9MrBf018448 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Sat, 27 Sep 2008 02:22:53 -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 <0K7U00401KQ5H100@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Sat, 27 Sep 2008 02:22:53 -0700 (PDT) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K7U002FTKQ3XEF0@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Sat, 27 Sep 2008 02:22:52 -0700 (PDT) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m8R9MpZx016567 for ; Sat, 27 Sep 2008 09:22:51 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0K7U00L01KEEI000@mail-apac.sun.com> (original mail from Ryan.Wang@Sun.COM) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Sat, 27 Sep 2008 17:22:51 +0800 (SGT) Received: from [127.0.0.1] ([60.20.4.169]) by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0K7U00M6YKPQ9V9E@mail-apac.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Sat, 27 Sep 2008 17:22:51 +0800 (SGT) Date: Sat, 27 Sep 2008 17:22:39 +0800 From: Yu-Bo Ryan Wang Subject: Re: approved in 7/23 meeting [Re: RaidCfg GUID and volume activation support [PSARC/2008/458 FastTrack timeout 07/24/2008]] In-reply-to: <18652.52504.463746.851318@gargle.gargle.HOWL> Sender: Ryan.Wang@Sun.COM To: James Carlson Cc: Tzongyu.Lee@Sun.COM, PSARC-ext@Sun.COM, Jie Jerend Cao Message-id: <48DDFB5F.6030205@Sun.COM> MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_zdWNwtbstZPzMTlXZe03bw)" X-PMX-Version: 5.4.1.325704 References: <200807180157.m6I1vsS8001924@sac.sfbay.sun.com> <48877E4A.5090700@Sun.COM> <48DB5E52.40501@Sun.COM> <18651.32747.974163.425806@gargle.gargle.HOWL> <48DC3E9C.7040305@Sun.COM> <18652.52504.463746.851318@gargle.gargle.HOWL> User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) Status: RO Content-Length: 3933 This is a multi-part message in MIME format. --Boundary_(ID_zdWNwtbstZPzMTlXZe03bw) Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT Hi James, Please see my in-line comments. Thanks, Ryan James Carlson wrote: > Yu-Bo Ryan Wang writes: > >> For the output change, as the section 4.3 mentioned, >> >> GUID information output had been added to disk information display >> in a compatible format. And for a given volume, if it's in inactive >> state, array information display output will show this status. See >> accompanied diff file for the raidctl manpage. >> >> Currently, there is nothing dependent on that output. >> > > I'm a little surprised that adding a field in the middle of a table is > considered a "compatible format," particularly so in a patch, but if > we're absolutely sure that there's nothing dependent on this but human > eyeballs, then it seems ok to me. > We are sure that there's no dependent on this because raidctl is a config tool for RAID and it's not a frequently used software; and according to our survey during the research period, the only possible exception (besides human eyeballs) is the exit status checking, and this is un-changed. > Please do make sure that when the man page is updated, the stability > is updated to the current terminology (what was once "Evolving" is now > "Committed"), and that the man page makes clear that the stability > applies to the command line arguments only, as the output from this > command (as this project makes plain) is substantially less than > "Committed." It's probably "Volatile" at best. > > Agree. We will do this when updating the man page. --Boundary_(ID_zdWNwtbstZPzMTlXZe03bw) Content-type: text/html; charset=ISO-8859-1 Content-transfer-encoding: 7BIT Hi James,

Please see my in-line comments.

Thanks,
Ryan


James Carlson wrote: 
Yu-Bo Ryan Wang writes:
  
For the output change, as the section 4.3  mentioned,

        GUID information output had been added to disk information display
	in a compatible format. And for a given volume, if it's in inactive
        state, array information display output will show this status. See
	accompanied diff file for the raidctl manpage.

Currently, there is nothing dependent on that output.
    

I'm a little surprised that adding a field in the middle of a table is
considered a "compatible format," particularly so in a patch, but if
we're absolutely sure that there's nothing dependent on this but human
eyeballs, then it seems ok to me.
We are sure that there's no dependent on this because raidctl is a config tool
for RAID and it's not a frequently used software; and according to our survey
during the research period, the only possible exception (besides human eyeballs)
is the exit status checking, and this is un-changed. 
Please do make sure that when the man page is updated, the stability
is updated to the current terminology (what was once "Evolving" is now
"Committed"), and that the man page makes clear that the stability
applies to the command line arguments only, as the output from this
command (as this project makes plain) is substantially less than
"Committed."  It's probably "Volatile" at best.
Agree. We will do this when updating the man page. --Boundary_(ID_zdWNwtbstZPzMTlXZe03bw)-- From Tzongyu.Lee@sun.com Sat Sep 27 22:55:28 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m8S5tRsC026347 for ; Sat, 27 Sep 2008 22:55:28 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m8S5tPZx028644 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Sun, 28 Sep 2008 06:55:26 +0100 (BST) 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 <0K7W00H055SDE800@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Sat, 27 Sep 2008 22:55:25 -0700 (PDT) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K7W00D485SBWZ30@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Sat, 27 Sep 2008 22:55:24 -0700 (PDT) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m8S5tNQr023024 for ; Sun, 28 Sep 2008 05:55:23 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0K7W00B0158P5400@mail-apac.sun.com> (original mail from Tzongyu.Lee@Sun.COM) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Sun, 28 Sep 2008 13:55:23 +0800 (SGT) Received: from [129.158.218.85] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0K7W001B55S46510@mail-apac.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Sun, 28 Sep 2008 13:55:22 +0800 (SGT) Date: Sun, 28 Sep 2008 13:53:15 +0800 From: Tzongyu Paul Lee Subject: Re: approved in 7/23 meeting [Re: RaidCfg GUID and volume activation support [PSARC/2008/458 FastTrack timeout 07/24/2008]] In-reply-to: <48DDFB5F.6030205@Sun.COM> Sender: Tzongyu.Lee@sun.com To: Yu-Bo Ryan Wang Cc: James Carlson , PSARC-ext@sun.com, Jie Jerend Cao Reply-to: Tzongyu.Lee@sun.com Message-id: <48DF1BCB.6020205@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=UTF-8 Content-transfer-encoding: 8BIT X-PMX-Version: 5.4.1.325704 References: <200807180157.m6I1vsS8001924@sac.sfbay.sun.com> <48877E4A.5090700@Sun.COM> <48DB5E52.40501@Sun.COM> <18651.32747.974163.425806@gargle.gargle.HOWL> <48DC3E9C.7040305@Sun.COM> <18652.52504.463746.851318@gargle.gargle.HOWL> <48DDFB5F.6030205@Sun.COM> User-Agent: Thunderbird 2.0.0.4 (X11/20070723) Status: RO Content-Length: 1816 Yu-Bo Ryan Wang 写道: > Hi James, > > Please see my in-line comments. > > Thanks, > Ryan > > > James Carlson wrote: >> Yu-Bo Ryan Wang writes: >> >>> For the output change, as the section 4.3 mentioned, >>> >>> GUID information output had been added to disk information display >>> in a compatible format. And for a given volume, if it's in inactive >>> state, array information display output will show this status. See >>> accompanied diff file for the raidctl manpage. >>> >>> Currently, there is nothing dependent on that output. >>> >> >> I'm a little surprised that adding a field in the middle of a table is >> considered a "compatible format," particularly so in a patch, but if >> we're absolutely sure that there's nothing dependent on this but human >> eyeballs, then it seems ok to me. >> > We are sure that there's no dependent on this because raidctl is a > config tool > for RAID and it's not a frequently used software; and according to our > survey > during the research period, the only possible exception (besides human > eyeballs) > is the exit status checking, and this is un-changed. >> Please do make sure that when the man page is updated, the stability >> is updated to the current terminology (what was once "Evolving" is now >> "Committed"), and that the man page makes clear that the stability >> applies to the command line arguments only, as the output from this >> command (as this project makes plain) is substantially less than >> "Committed." It's probably "Volatile" at best. >> >> > Agree. We will do this when updating the man page. I suggest to file a CR/RFE to capture this so that this will be reflected when you next do any putback related to this. -- Tzongyu Paul Lee, Tzongyu.Lee@Sun.Com or Paul.Lee@Sun.COM BJS05 7225, x84343