From owner-freebsd-stable@FreeBSD.ORG Mon Jun 29 09:58:40 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 54EEF1065697 for ; Mon, 29 Jun 2009 09:58:40 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from kagate.punkt.de (kagate.punkt.de [217.29.33.131]) by mx1.freebsd.org (Postfix) with ESMTP id D86E58FC23 for ; Mon, 29 Jun 2009 09:58:39 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from hugo10.ka.punkt.de (hugo10.ka.punkt.de [10.0.0.110]) by kagate1.punkt.de with ESMTP id n5T9hxuD091068 for ; Mon, 29 Jun 2009 11:44:00 +0200 (CEST) Received: from hugo10.ka.punkt.de (localhost [127.0.0.1]) by hugo10.ka.punkt.de (8.14.2/8.14.2) with ESMTP id n5T9hxNx024504 for ; Mon, 29 Jun 2009 11:43:59 +0200 (CEST) (envelope-from ry93@hugo10.ka.punkt.de) Received: (from ry93@localhost) by hugo10.ka.punkt.de (8.14.2/8.14.2/Submit) id n5T9hxK1024503 for freebsd-stable@freebsd.org; Mon, 29 Jun 2009 11:43:59 +0200 (CEST) (envelope-from ry93) Date: Mon, 29 Jun 2009 11:43:59 +0200 From: "Patrick M. Hausen" To: FreeBSD Stable Mailing List Message-ID: <20090629094359.GB24054@hugo10.ka.punkt.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.5.17 (2007-11-01) Subject: Zpool on raw disk and weird GEOM complaint X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jun 2009 09:58:41 -0000 Hi, all, I have a system with 12 S-ATA disks attached that I set up as a raidz2: %zpool status zfs pool: zfs state: ONLINE scrub: scrub in progress for 0h5m, 7.56% done, 1h3m to go config: NAME STATE READ WRITE CKSUM zfs ONLINE 0 0 0 raidz2 ONLINE 0 0 0 da0 ONLINE 0 0 0 da1 ONLINE 0 0 0 da2 ONLINE 0 0 0 da3 ONLINE 0 0 0 da4 ONLINE 0 0 0 da5 ONLINE 0 0 0 da6 ONLINE 0 0 0 da7 ONLINE 0 0 0 da8 ONLINE 0 0 0 da9 ONLINE 0 0 0 da10 ONLINE 0 0 0 da11 ONLINE 0 0 0 errors: No known data errors We are currently tweaking kernel memory a bit but the on disk data and the hardware seem to be just fine. 7-STABLE, amd64, 4 GB of RAM. A couple of days ago, at each boot we saw this error message: GEOM: da0: corrupt or invalid GPT detected. GEOM: da0: GPT rejected -- may not be recoverable. There should not be any partition, MBR or GPT on the disks, I created the zpool on the raw devices. So I figure: Somehow zfs wrote some data to da0 that somewhat resembles a GPT partition table, so GEOM gets confused at boot time. Question is: can somebody confirm my guess? If yes should I just ignore the message, can it be disabled somehow (compile kernel without GPT?) or should zpools be created on slices instead of disks? Thanks for any hints, Patrick -- punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 info@punkt.de http://www.punkt.de Gf: Jürgen Egeling AG Mannheim 108285