Date: Wed, 10 Feb 2010 10:18:49 +0100 From: =?UTF-8?Q?Marius_N=C3=BCnnerich?= <marius@nuenneri.ch> To: =?UTF-8?B?R2Vycml0IEvDvGhu?= <gerrit@pmp.uni-hannover.de> Cc: Elliot Finley <efinley.lists@gmail.com>, freebsd-stable@freebsd.org Subject: Re: zpool vdev vs. glabel Message-ID: <b649e5e1002100118p14552a41r9bf7f48b540e5a74@mail.gmail.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
2010/2/10 Gerrit K=C3=BChn <gerrit@pmp.uni-hannover.de>:
> On Tue, 9 Feb 2010 13:27:21 -0700 Elliot Finley <efinley.lists@gmail.com>
> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b649e5e1002100118p14552a41r9bf7f48b540e5a74>