From owner-freebsd-current@FreeBSD.ORG Wed Oct 5 15:40:37 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E5CAB106568E; Wed, 5 Oct 2011 15:40:37 +0000 (UTC) (envelope-from swhetzel@gmail.com) Received: from mail-dy0-f54.google.com (mail-dy0-f54.google.com [209.85.220.54]) by mx1.freebsd.org (Postfix) with ESMTP id 553498FC24; Wed, 5 Oct 2011 15:40:37 +0000 (UTC) Received: by dyj4 with SMTP id 4so130322dyj.13 for ; Wed, 05 Oct 2011 08:40:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=OKitPAMJp9kvs6kOss+4IH7m1hzZb1MQS+dfgDtbidA=; b=sova6deSc3GMmByzP5vgo+AKe9yvdoY4GyGnhVM1Ob3A+hCcKfGdCV85RD6PcLT3rr jxGPQlgP+AnPsF7ID00tSU3VESFcYqFIgnw+VIjGJ/AInhmZ9GPaTnRJ11s0oVSRuvJc aDxpTt8tvfZDw5l0hnRl3/5jiR/rLDDYnVhRo= MIME-Version: 1.0 Received: by 10.223.11.23 with SMTP id r23mr1442299far.38.1317827526866; Wed, 05 Oct 2011 08:12:06 -0700 (PDT) Received: by 10.152.6.36 with HTTP; Wed, 5 Oct 2011 08:12:06 -0700 (PDT) In-Reply-To: <4E8C6E85.90005@quip.cz> References: <1927112464.20111004220507@serebryakov.spb.ru> <4E8B7A27.5070908@quip.cz> <344794801.20111005101957@serebryakov.spb.ru> <4E8C1426.60107@quip.cz> <251861322.20111005125825@serebryakov.spb.ru> <4E8C6E85.90005@quip.cz> Date: Wed, 5 Oct 2011 10:12:06 -0500 Message-ID: From: Scot Hetzel To: Miroslav Lachman <000.fbsd@quip.cz> Content-Type: text/plain; charset=ISO-8859-1 Cc: current@freebsd.org, freebsd-geom@freebsd.org Subject: Re: RFC: Project geom-events X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2011 15:40:38 -0000 2011/10/5 Miroslav Lachman <000.fbsd@quip.cz>: > I am waiting years for the moment, when these GEOM problems will be fixed, > so I am really glad to see your interest! > It will be move to right direction even if changes will not be backward > compatible. > The current state is too fragile to be used in production. Gmirror alone can > be used, glabel alone can be used, GPT alone can be used... but mix it all > stacked together is way to hell. > > e.g. Using GPT on glabeled provider always ends with error message about > corrupted secondary GPT table. (But how can I use iSCSI in reliable way if I > cannot use glable on devices and iSCSI device can have different number on > each reboot? I wrote about it almost 2 years ago) > You don't need to use glabel on GPT disks, as gpart has it's own way to label GPT disks: Fixit# gpart create -s gpt ad0 Fixit# gpart add -s 4G -t freebsd-swap -l swap0 ad0 Fixit# gpart add -t freebsd-zfs -l disk0 ad0 This create the following in /dev: /dev/gpt/swap0 /dev/gpt/disk0 Glabel is not needed for GPT partitioned disks. What should happen is that glabel should fail when attempting to label a GPT disk. If you wish to add a GPT label after the fact use: gpart show geom gpart modify -i index -l label geom (i.e. geom = ad0) Scot