From owner-freebsd-geom@FreeBSD.ORG Thu Mar 12 10:19:04 2009 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E4269106564A for ; Thu, 12 Mar 2009 10:19:04 +0000 (UTC) (envelope-from ulf.lilleengen@gmail.com) Received: from mail-ew0-f166.google.com (mail-ew0-f166.google.com [209.85.219.166]) by mx1.freebsd.org (Postfix) with ESMTP id 69AAD8FC08 for ; Thu, 12 Mar 2009 10:19:04 +0000 (UTC) (envelope-from ulf.lilleengen@gmail.com) Received: by ewy10 with SMTP id 10so441278ewy.43 for ; Thu, 12 Mar 2009 03:19:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=e3n7pDUzxtoNV1gNYVMWoaymXj5Aom0aZu08gK1ZfIQ=; b=h7bwelchEiUOcKX8TvtkKwVZvrqyCvSclRFWn8AgQRg0ZXF2CvpbRkQjLfzxB9sZ9D bQhcMzKnu3VREx+aZWYeSDZx/b/sppW11SyvUH9CT5yfY9fbwBrY6lNczBMgOuHRUmwg JQUoZFEVlmjsKIH+1FYJcBdsXXRNZtX7g7vq4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=xgZDGMFSOvtpbpDCOx4r6FEEJghoPVzzxhUWHxvcpDbN7eqLMsq7EDAR5FwmJwMm4F FwJv5wTjfyQ4J0sKj1ulADOyuykXLsLKR1TofmOP5ZcpwzXV0E/oV3eT5tP/Vwe+BMKP 081Bav9kGawE7Xfwh6nTbmr+BdmKei2chXIXg= MIME-Version: 1.0 Received: by 10.216.8.212 with SMTP id 62mr3888813wer.160.1236851826445; Thu, 12 Mar 2009 02:57:06 -0700 (PDT) In-Reply-To: <6D5ADA2B-9471-4404-892D-1DFAB9011C09@bitheaven.net> References: <6D5ADA2B-9471-4404-892D-1DFAB9011C09@bitheaven.net> Date: Thu, 12 Mar 2009 10:57:06 +0100 Message-ID: <917871cf0903120257u40537e4fp47b6d3ab973f706@mail.gmail.com> From: Ulf Lilleengen To: Clayton Fuller Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-geom@freebsd.org Subject: Re: Safe to ignore GEOM warnings on ZFS raidz? X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Mar 2009 10:19:05 -0000 On Thu, Mar 12, 2009 at 8:52 AM, Clayton Fuller wrote: > I am setting up a new home file server on CURRENT-8.0 using 4 1.5 TB SATA > drives in a ZFS raidz pool > I created the pool without first partitioning or labeling the drives. > > during the boot sequence, I get the following warnings for each of the > drives: > GEOM: ad6: corrupt or invalid GPT detected. > GEOM: ad6: GPT rejected -- may not be recoverable. > > here's the drive info (I have 3 identical drives at ad8, ad12 and ad14) > ad6: 1430799MB at ata3-master SATA300 > > The storage pool seems to work fine, as tested by transferring nearly a > terabyte of data, simulating a failed drive, resilvering, etc and all seems > to be working well. > > invoking the zpool scrub command will bring up the corrupt GPT > errors again, but all other read/write operations on my storage pool seem to > be fine. > > Is GEOM in any way necessary for managing this ZFS pool? Can I safely > ignore the warnings? Is there a better way to configure this to keep GEOM > happy? > This has not necessarily anything to do with the pool itself, but gpart will display this message in case it finds remains of an old GPT partition. I think you can ignore the warnings. At least they have posed no problem from me for a while now. > > I'd be happy to supply more specifics if germane, but thought I'd try to > keep it simple. > > Any suggestions would be greatly appreciated. > > -Clayton > _______________________________________________ > freebsd-geom@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-geom > To unsubscribe, send any mail to "freebsd-geom-unsubscribe@freebsd.org" > -- Ulf Lilleengen