From owner-freebsd-hackers@freebsd.org Mon Jul 30 00:52:37 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CC84F106875A for ; Mon, 30 Jul 2018 00:52:37 +0000 (UTC) (envelope-from dcrosstech@gmail.com) Received: from mail-qt0-x22b.google.com (mail-qt0-x22b.google.com [IPv6:2607:f8b0:400d:c0d::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 68F9E81983 for ; Mon, 30 Jul 2018 00:52:37 +0000 (UTC) (envelope-from dcrosstech@gmail.com) Received: by mail-qt0-x22b.google.com with SMTP id a5-v6so10482211qtp.2 for ; Sun, 29 Jul 2018 17:52:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=sjj89xXkI/mZlSc2TGabSbJCpZUHkKEpr6IXFZnN/4Y=; b=K9ZbjyIuqCisIzsP+6TNWXdMh2LIzZ2CoxzOPFluDVcTP2XaQJmod5yd5v+bMUOPSK R5GUmGltDRX/6oWpsgdgBQ6TKzHhpv+NVtQxdL9SKe1u6ldZD0i5XERYRTmfk6JjonlF zG3930M3Eg5fcjNcRQjobddIKN5pK862BXaxEKGL0i31kfwwmnP76+fRSCWJDFHYXSN5 lclOOS7eDIEpdke2CUrDRFQ9oxCjFkOz7oeUPz+FfPIu0X4Ovp+c8RXdRXnpT5TKjgHk +zHN5ToGf/loguGca4Dl9WIGXkwxFXIZj3pJZ6tvnv5yMhcVa9g0VcnAZukfRD6y8M7Q S5Tw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=sjj89xXkI/mZlSc2TGabSbJCpZUHkKEpr6IXFZnN/4Y=; b=QUGUInwvDfhSwQ1UhIS4koh2BDVsEmNbDsF++e/Y6m1yg5u/Gdpr8ByTJcWKqw/ijl yOsXkEtwPIgKBNAP+mBIm2LstFP/DLOJKTvKWjB1ZXxvuxV3yi+WMO+P6AL/nxh4I2aG hT51GvdKlWskC0QJyRDcOA50tmDzQuRFV2Mp1VVxMzj28vPgmAU+eL1/UhKYPN9Jstht GYwt7s2DXzAfwZ0PobDZSK6rTV6vmuAmvUhHNpDUWosl8Jo3qzvwmesv5riFZIVa4Tiz sN28gOJKxgISMEcmmIRbXDFjk3MKVPS8b4XbJx/NfTlIaUROk3hIUiNtuMiJ+zRnNrnb SBtQ== X-Gm-Message-State: AOUpUlEgNRwcB62wFzeOYNF6cTPM42b8ecQwM/YexX3dX+qKetIz3mli WnsUpmahXvTHU9rsQHt4WyN9Yedr X-Google-Smtp-Source: AAOMgpfgjetBmN9C+DtXtKCTC1cxpwjIwCbsH0uue2A1jnK+cnXIviqgsZrQo8NfBOjEzhYZKtlPng== X-Received: by 2002:ac8:524f:: with SMTP id y15-v6mr14451094qtn.227.1532911956911; Sun, 29 Jul 2018 17:52:36 -0700 (PDT) Received: from [10.1.6.133] (cpe-66-66-97-162.rochester.res.rr.com. [66.66.97.162]) by smtp.gmail.com with ESMTPSA id m15-v6sm7483612qki.44.2018.07.29.17.52.36 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 29 Jul 2018 17:52:36 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: Request for comments, new geom part type alias: freebsd-geom From: David Cross X-Mailer: iPhone Mail (15G77) In-Reply-To: <201807292102.w6TL2Cq4062739@pdx.rh.CN85.dnsmgr.net> Date: Sun, 29 Jul 2018 20:52:35 -0400 Cc: FreeBSD Hackers Content-Transfer-Encoding: quoted-printable Message-Id: <144DA23D-26CF-4293-AE97-54CC8D6B52E3@gmail.com> References: <201807292102.w6TL2Cq4062739@pdx.rh.CN85.dnsmgr.net> To: "Rodney W. Grimes" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jul 2018 00:52:38 -0000 Just a named GPT UUID type, like freebsd-swap, freebsd-ufs As for ambiguous data: consider you have a RAID 10 of a UFS filesystem. If y= ou put that into freebsd-ufs freebsd-boot will see that and potentially atte= mpt to boot it. If you have a raw raid gstripe, what shows up to the BIOS a= s to what this drives is depends entirely on the _contents_ of the drive at a= specific position, information that could be controlled by a user. So to '= the bios' the meaning is what the OS put there, but the OS put user data the= re; how does the OS control the intent (as the BIOS sees it) of that data? On Jul 29, 2018, at 17:02, Rodney W. Grimes wrote: >> I'd like to propose that we create a GPT partition for geom labeled >> partitions (gmirror, gstripe, geli, etc.. anything that can be 'tasted' a= nd >> automatically determined.) called 'freebsd-geom'. >>=20 >> There are numerous cases where you shouldn't have a raw geom on a disk (f= or >> example, imagine a raid 10 of a filesystem with VMs on it..on a raw disk >> its possible that the lead block happens to line up with a VM disk image o= r >> anything else a BIOS may determine is bootable). >>=20 >> So the question becomes which part id to use; IF its a mirror of a swap o= f >> UFS it seems perfectly reasonable to use freebsd-swap or freebsd-ufs (if a= >> bit dangerous). If its a mirror or a geli then you can again be in the >> situation where the boot blocks (or something else), in certain >> circumstances mistakes these for raw filesystems with similarly calamitou= s >> results. >>=20 >> Given these, it seems a 'freebsd-geom' (or similar) seems entirely >> appropriate; we can mark these for what they really are, and eliminate >> these cases where the system misinterprets intentions based on ambiguous >> data. >=20 > Do you have more details on just how your going to implement a "GPT" > partition for geom labeled partitions. Though I think I understand > what it is you want to do, how you describe it leads to some confusion > on just what you are desiring to do. >=20 > I am aware of some major issues involving gmultipath (GEOM::MULTIPATH) > and gpt partitioned disks (GEOM::GPT) that due to bad tasting priorities > you get bogus GPT error messages during boot if you have labeled your > gmultipath devices, and infact can damage a gpt disk if you apply a > multipath label onto a valid gpt disk. =20 >=20 > Please describe the "ambiguous data" as well, as I am not aware of > what that would be. >=20 > Thanks, > --=20 > Rod Grimes rgrimes@freebsd= .org