From owner-freebsd-questions@freebsd.org Sun Jun 28 22:10:22 2015 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 88DA898F6F9 for ; Sun, 28 Jun 2015 22:10:22 +0000 (UTC) (envelope-from quartz@sneakertech.com) Received: from douhisi.pair.com (douhisi.pair.com [209.68.5.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 68BB61665 for ; Sun, 28 Jun 2015 22:10:22 +0000 (UTC) (envelope-from quartz@sneakertech.com) Received: from [10.2.2.1] (pool-173-48-121-235.bstnma.fios.verizon.net [173.48.121.235]) by douhisi.pair.com (Postfix) with ESMTPSA id 9E3173F6E8 for ; Sun, 28 Jun 2015 18:10:20 -0400 (EDT) Message-ID: <559070CC.8040105@sneakertech.com> Date: Sun, 28 Jun 2015 18:10:20 -0400 From: Quartz User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: freebsd-questions Subject: Re: Corrupt GPT on ZFS full-disks that shouldn't be using GPT References: <558F99B6.2080205@sneakertech.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Jun 2015 22:10:22 -0000 > Unfortunately on one of the 11 groups I forgot to perform the "gpart > destroy" step. OK, well you should still get a readout of all the gpt stuff off the disks just to make sure you're not doing something elsewhere that actually needs gpt (like labels or something). In this case though you can compare the 'good' drives to the 'bad' drives. > What I means to say was "offline the drive, dd if=/dev/zero > the drive, then resilver it. > Do I need to export the pool before using dd on the > raw device? Given that this is a raidz3 and you're just going to dd nuke a single drive, then no. Just offline the drive first so the pool's not trying to use it. Exporting a pool completely shuts it down and packages everything up in a machine-independent way so it can be physically moved to a new box, but that's overkill for your situation. (Also, I'm not 100% sure what zfs does when you try to import a pool with one drive "missing"). > What I meant here was to say "Perhaps I can politely ask ZFS 'hey if > you are not using the last 512 bytes of these devices, would you mind > just filling that with zeros?'". I would feel more comfortable if > there was a command like that offered by ZFS rather than me just using > dd and hoping it doesn't interfere with ZFS. I *think* that zfs is like other file system partitioning schemes in that it just writes from the beginning of the drive and doesn't care about the end until it gets there... however don't quote me on it. Again though, you could always offline the drive, dd the end, then reattach it and do a scrub or something. If you end up blowing away something zfs needs, it won't stay silent about it.