From owner-freebsd-fs@FreeBSD.ORG Wed Nov 26 00:02:32 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BA6D59D7 for ; Wed, 26 Nov 2014 00:02:32 +0000 (UTC) Received: from forward5l.mail.yandex.net (forward5l.mail.yandex.net [IPv6:2a02:6b8:0:1819::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Certum Level IV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 75ED0C98 for ; Wed, 26 Nov 2014 00:02:32 +0000 (UTC) Received: from smtp2m.mail.yandex.net (smtp2m.mail.yandex.net [77.88.61.129]) by forward5l.mail.yandex.net (Yandex) with ESMTP id EB3CAC40F9C; Wed, 26 Nov 2014 03:02:28 +0300 (MSK) Received: from smtp2m.mail.yandex.net (localhost [127.0.0.1]) by smtp2m.mail.yandex.net (Yandex) with ESMTP id 78ABA420059; Wed, 26 Nov 2014 03:02:28 +0300 (MSK) Received: from 84.201.166.117-vpn.dhcp.yndx.net (84.201.166.117-vpn.dhcp.yndx.net [84.201.166.117]) by smtp2m.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id rLYqZcawSd-2SQ4ujh8; Wed, 26 Nov 2014 03:02:28 +0300 (using TLSv1.2 with cipher AES128-SHA (128/128 bits)) (Client certificate not present) X-Yandex-Uniq: 09614d4c-89d1-42a5-aec6-72b53c2d9af2 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1416960148; bh=4LeJ/eOPjJ3A0o6drjTYmpIBINZt9+USrIQeWhdyx/Q=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:Subject: References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=N6hLQrTlT4uZJgebNz4JIff02ENy4hjEZ9eEpORdQxWp6SASXZQ9rXb3TTDx+ACNr UXI4OLKyO5XvB4ZSVU3kprH6wAGeL4yFJmRT1MCpmfOZjsPAmu/7tMollV/yNoI3LX NuFT3h42gR90Hs3Z9Dcvp6VxrcaFnGPcQgcxKw9o= Authentication-Results: smtp2m.mail.yandex.net; dkim=pass header.i=@yandex.ru Message-ID: <54751876.3070801@yandex.ru> Date: Wed, 26 Nov 2014 03:01:58 +0300 From: "Andrey V. Elsukov" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Michael Dexter , freebsd-fs@freebsd.org Subject: Re: How to manually validate a gpart layout? References: <547502A9.5060903@callfortesting.org> In-Reply-To: <547502A9.5060903@callfortesting.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Nov 2014 00:02:32 -0000 On 26.11.2014 01:28, Michael Dexter wrote: > The kernel will report this at boot if a primary GPT is invalid: > > GEOM: da1: the primary GPT table is corrupt or invalid > > How does one manually validate the table with gpart? I sense that 'gpart > recover' will perform enough of a test to say that recovery is not > needed but it is not clear if this is the same test that the kernel is > performing. Hi, gpart(8) only sends control requests to the kernel, it doesn't do any tests. -- WBR, Andrey V. Elsukov