From owner-freebsd-stable@FreeBSD.ORG Wed Feb 10 09:19:10 2010 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 D87BB10657A4 for ; Wed, 10 Feb 2010 09:19:10 +0000 (UTC) (envelope-from marius@nuenneri.ch) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.25]) by mx1.freebsd.org (Postfix) with ESMTP id 781D28FC0C for ; Wed, 10 Feb 2010 09:19:10 +0000 (UTC) Received: by ey-out-2122.google.com with SMTP id 25so1041766eya.3 for ; Wed, 10 Feb 2010 01:19:09 -0800 (PST) MIME-Version: 1.0 Received: by 10.216.88.79 with SMTP id z57mr1149331wee.22.1265793549344; Wed, 10 Feb 2010 01:19:09 -0800 (PST) In-Reply-To: <20100210092412.5a06d98e.gerrit@pmp.uni-hannover.de> References: <20100209150606.ddba52dc.gerrit@pmp.uni-hannover.de> <54e63c321002091227w15657c54oeb2295efc4c43980@mail.gmail.com> <20100210092412.5a06d98e.gerrit@pmp.uni-hannover.de> From: =?UTF-8?Q?Marius_N=C3=BCnnerich?= Date: Wed, 10 Feb 2010 10:18:49 +0100 Message-ID: To: =?UTF-8?B?R2Vycml0IEvDvGhu?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: Elliot Finley , freebsd-stable@freebsd.org Subject: Re: zpool vdev vs. glabel 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: Wed, 10 Feb 2010 09:19:10 -0000 2010/2/10 Gerrit K=C3=BChn : > On Tue, 9 Feb 2010 13:27:21 -0700 Elliot Finley > wrote about Re: zpool vdev vs. glabel: > > EF> I ran into this same problem. =C2=A0you need to clean the beginning a= nd end > EF> of your disk off before glabeling and adding it to your pool. =C2=A0c= lean > EF> with dd if=3D/dev/zero... > > Hm, I think I did that (at least for the beginning part). > Maybe I was not quite clear what I did below: I removed and re-attached > the *same* disk which was labelled with glabel and running fine brefore. > The label was there when I inserted it back, but zfs went for the da > device node anyway. > If I see this problem again, I will try to wipe the complete disk before > re-inserting it. It seems there is some kind of race condition with zfs either picking up the disk itself or the label device for the same disk. I guess it's which ever it probes first. I wrote the GPT part of glabel for using it in situations like this, I had not a single report of this kind of problem with the gpt labels. Maybe you can try them too? My zpool looks like this: % zpool status pool: tank state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 0 raidz2 ONLINE 0 0 0 gpt/wd1 ONLINE 0 0 0 gpt/wd2 ONLINE 0 0 0 gpt/wd3 ONLINE 0 0 0 gpt/wd4 ONLINE 0 0 0 gpt/wd5 ONLINE 0 0 0 errors: No known data errors I already physically reordered the devices a few times and it always worked out correctly.