From owner-freebsd-stable@FreeBSD.ORG Tue Jul 7 22:40:06 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 2F4521065670 for ; Tue, 7 Jul 2009 22:40:06 +0000 (UTC) (envelope-from dan.naumov@gmail.com) Received: from mail-yx0-f181.google.com (mail-yx0-f181.google.com [209.85.210.181]) by mx1.freebsd.org (Postfix) with ESMTP id D95488FC0A for ; Tue, 7 Jul 2009 22:40:05 +0000 (UTC) (envelope-from dan.naumov@gmail.com) Received: by yxe11 with SMTP id 11so7426582yxe.3 for ; Tue, 07 Jul 2009 15:40:05 -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 :content-transfer-encoding; bh=AjV901ikXi/KBOLdHkXocNpdhNWycdt/ouVzvbqCM1g=; b=eiOQAg/xM2akguy9UUZD1EnSDN+HonUTu1Fep8xmn9BUcIC/grAIxDxxXZfaT95lZM gu4+7axedhkPWYnFi6BOOfotWqEW4/p4afnHgoXvOS81HLmZJ5Guyyy3eJbjRsVRkRh0 /xM/f76F8m+Zz8Gqu5NozFmDGJ4TkA9nveES4= 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:content-transfer-encoding; b=eeGMs5htn5JHb+5jaWwbQq//So5D6srOsjH4YnR9j4mGYVkEqBakvN9T92dAbahx9V 3kdxyPhYl5QGQg5n1gajWnf2WjUT3z03+MadsED5fgN3X7bFpSKW0rZ3ZGWhp/YrHM+i CM4NJ1adw4XgXSXemd7kwdDywV9JqvjSiSFYo= MIME-Version: 1.0 Received: by 10.100.166.10 with SMTP id o10mr11394301ane.126.1247006404219; Tue, 07 Jul 2009 15:40:04 -0700 (PDT) In-Reply-To: References: <20090707195614.GA24326@martini.nu> <20090707222631.GA70750@martini.nu> Date: Wed, 8 Jul 2009 01:40:02 +0300 Message-ID: From: Dan Naumov To: Freddie Cash Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: ZFS: drive replacement performance 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: Tue, 07 Jul 2009 22:40:06 -0000 On Wed, Jul 8, 2009 at 1:32 AM, Freddie Cash wrote: > On Tue, Jul 7, 2009 at 3:26 PM, Mahlon E. Smith wrote= : > >> On Tue, Jul 07, 2009, Freddie Cash wrote: >> > >> > This is why we've started using glabel(8) to label our drives, and the= n >> add >> > the labels to the pool: >> > =A0 # zpool create store raidz1 label/disk01 label/disk02 label/disk03 >> > >> > That way, it does matter where the kernel detects the drives or what t= he >> > physical device node is called, GEOM picks up the label, and ZFS uses = the >> > label. >> >> Ah, slick. =A0I'll definitely be doing that moving forward. =A0Wonder if= I >> could do it piecemeal now via a shell game, labeling and replacing each >> individual drive? =A0Will put that on my "try it" list. Not to derail this discussion, but can anyone explain if the actual glabel metadata is protected in any way? If I use glabel to label a disk and then create a pool using /dev/label/disklabel, won't ZFS eventually overwrite the glabel metadata in the last sector since the disk in it's entirety is given to the pool? Or is every filesystem used by FreeBSD (ufs, zfs, etc) hardcoded to ignore the last few sectors of any disk and/or partition and not write data to it to avoid such issues? - Sincerely, Dan Naumov