From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=63.128.21.131; helo=us-smtp-delivery-131.mimecast.com; envelope-from=herbie.robinson@stratus.com; receiver=edk2-devel@lists.01.org Received: from us-smtp-delivery-131.mimecast.com (us-smtp-delivery-131.mimecast.com [63.128.21.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 88CC8210F16B8 for ; Tue, 3 Jul 2018 10:12:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=StratusTechnologies.onmicrosoft.com; s=selector1-stratus-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=vlm+M+3vhhpXIfnUJT1F1wOPiWwitvJt3eiW5N7NTjc=; b=JgRt3g1JwMY1/GBUAVki07b1LdR/KqqSUj/1iQkcZ28JCBulMffsLhsepidvGJIxEciOdL0EzF7+1WR85xPndKPLh5oVn9q/wyY9G+zVO37/4E+xkVAY9AI21zzUY//5YHAjq+h9dB4ZGJ6zlB/m1fzFMBnS9Hrb644rywM1D6A= Received: from NAM03-DM3-obe.outbound.protection.outlook.com (mail-dm3nam03lp0021.outbound.protection.outlook.com [207.46.163.21]) (Using TLS) by us-smtp-1.mimecast.com with ESMTP id us-mta-122-VZylRmzBNCOFjtw-drq2pw-1; Tue, 03 Jul 2018 13:12:39 -0400 Received: from BL2PR08MB100.namprd08.prod.outlook.com (10.242.196.24) by BL2PR08MB708.namprd08.prod.outlook.com (10.141.95.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.906.25; Tue, 3 Jul 2018 17:12:35 +0000 Received: from BL2PR08MB100.namprd08.prod.outlook.com ([fe80::2d1c:63e4:76b5:c4d1]) by BL2PR08MB100.namprd08.prod.outlook.com ([fe80::2d1c:63e4:76b5:c4d1%13]) with mapi id 15.20.0906.026; Tue, 3 Jul 2018 17:12:35 +0000 From: "Robinson, Herbie" To: "edk2-devel@lists.01.org" Thread-Topic: GPT Partitions on RAID Disks Thread-Index: AdQS5hbVjgw0qMUKRfa18LmaNMJwWg== Date: Tue, 3 Jul 2018 17:12:35 +0000 Message-ID: Accept-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [198.97.42.5] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; BL2PR08MB708; 7:YrRaGMJuJWhwqj9K6GDBIWVuSkz1U6L4tufjpnuOAdwmJ5OIWHPYOP4pLi7wvF/K7V76NQ8J1bN8pBsfya6nTis++U44wPOEkD8P1NtHP/hp5SC2Ag/3xX9cIxg31rTgQhwFYA6gcBWbPeeZMZK6ZOVh23GoO6RgSQUZCQN4D9g0Jd8f4bbub+yqIzaBW43ikr/nLMFcq5+3oicwH8RWxgTeWZKB/3GuIWh/uUCujVZHHtd092MOWJu6WnUN00Gm; 20:FtIcSuBHuBgaLM5zKALU1Jw0+VLGy0gtjrZxgTLjBVTvjyIMh9GOHxdEOO+ZXJ6XTRUHGVTM1tLecgkFFJwDZnExKDTMVvZ6bHPkc6jKXyy5Tw/ActGCzoHB/ZvjL/JKTdwpJfjjMcTpPgtAcpqT6OigrSHR8s9R/7e3C75Gp1A= x-ms-exchange-antispam-srfa-diagnostics: SOS; x-ms-office365-filtering-correlation-id: a299ad13-bd08-41d4-53f4-08d5e1082bf6 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989117)(5600053)(711020)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(2017052603328)(7153060)(49563074)(7193020); SRVR:BL2PR08MB708; x-ms-traffictypediagnostic: BL2PR08MB708: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(28532068793085)(35073007944872)(255031698444463)(788757137089)(32476226591037)(21748063052155); x-ms-exchange-senderadcheck: 1 x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(102415395)(6040522)(2401047)(8121501046)(5005006)(3231280)(944501410)(52105095)(10201501046)(93006095)(93001095)(3002001)(149027)(150027)(6041310)(20161123564045)(20161123560045)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(6072148)(201708071742011)(7699016); SRVR:BL2PR08MB708; BCL:0; PCL:0; RULEID:; SRVR:BL2PR08MB708; x-forefront-prvs: 0722981D2A x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(346002)(39850400004)(366004)(136003)(376002)(199004)(189003)(51874003)(5660300001)(861006)(8936002)(606006)(478600001)(53936002)(54896002)(790700001)(256004)(6306002)(26005)(186003)(7696005)(6116002)(5250100002)(2501003)(6916009)(74316002)(66066001)(99936001)(81166006)(81156014)(733005)(86362001)(8676002)(68736007)(72206003)(2351001)(5640700003)(15974865002)(99286004)(55016002)(97736004)(33656002)(2906002)(7736002)(316002)(14454004)(2900100001)(102836004)(105586002)(54556002)(25786009)(476003)(106356001)(3846002)(486006)(6436002)(9686003)(6506007)(236005); DIR:OUT; SFP:1102; SCL:1; SRVR:BL2PR08MB708; H:BL2PR08MB100.namprd08.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; x-microsoft-antispam-message-info: DM2nDKRbtLVPXjmvkNxfNALh1nKK3U0/KV2haNmM0L1OFdiq/gWCmR01o1MJD+Rw8vs05A9lEwYmTMZdwXJl8w4rMOB3iZS9Po9In9CsACbYOAlOjZuaRIyBjiMJ/a0ELhBIrU2S68zzs08amQlTa5hUZiAmzy2aZsEeLcPZ72hWc1iSjHP9D3wMTxj1BarrF3LhsYfPTfbWU1uB90zbMNL2zV5d3kV4hPOEKsP/9SZVNUrMOEeXcYa20LfDOmYGJzlp2763qJnFDd4WWNZNWmxdU+cJKBRKBxIOKB5N5I3LtjqeI51zS13fwiJqY5Qf9aIE0XmzFEzH2dMdaNZZQ3b2c31457o1trOlUJ6IOrY= spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-OriginatorOrg: stratus.com X-MS-Exchange-CrossTenant-Network-Message-Id: a299ad13-bd08-41d4-53f4-08d5e1082bf6 X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Jul 2018 17:12:35.5719 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: de36b473-b8ad-46ff-837f-9da16b8d1b77 X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL2PR08MB708 X-MC-Unique: VZylRmzBNCOFjtw-drq2pw-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.26 Subject: GPT Partitions on RAID Disks X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jul 2018 17:12:53 -0000 Content-Language: en-US Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable Background: I have been tasked with implementing UEFI boot in our VOS operating system.= We've been using GPT partitions for more than 15 years, but only within o= ur own OS... We haven't had to interact with any other software before thi= s. We have a fault tolerant OS; so, all disks are RAID1 (software supporte= d). We don't expose the GPT partitioning to our user interface: We have j= ust use it as a wrapper for boot support to keep BIOS from being confused. = The intent was to set it up to boot with either the legacy BIOS or UEFI. = At the time, we only had a legacy BIOS to test with; so, we never finished = the UEFI boot. I've reviewed our current implementation and found a few minor things wrong= ; so, I have been working on a utility to fix them. But the might be some = more issues. I have three questions, but relating to RAID 1. 1. We have historically paired entire disks when we do RAID1, not par= titions (we have never supported multiple file system partitions on one dis= k, because it didn't make sense from a performance standpoint). I believe = the current initialization uses the same DiskGUID in the GPT header for bot= h disks. I'm assuming that is not going to work properly. Is that correct= ? 2. The spec also seems to say that the UniquePartitionGUID should als= o be different for RAID 1 pairs. Is that correct? 3. We have learned over the years that one doesn't allocate an entire= disk for a RAID (because one may have to replace a drive and replacement m= ay not come with exactly the same ending LBA). We are currently leaving of= f some space at the end. When we do that, we are not putting the backup GP= T header at the last LBA the devices. By my reading of the spec, that is a= mistake. I do believe the spec allows me to leave a large gap between the= LastUsableLBA in the backup GPT header with the backup table placed anywhe= re within that gap. Is that correct? Thanks in advance for your guidance. Herbie Robinson Software Architect Stratus Technologies | www.stratus.com 5 Mill and Main Place, Suite 500 | Maynard, MA 01754 T: +1-978-461-7531 | E: Herbie.Robinson@stratus.com [Stratus Technologies]