Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 11 Sep 2014 06:15:14 +0300
From:      Kimmo Paasiala <kpaasial@icloud.com>
To:        Steven Hartland <killing@multiplay.co.uk>
Cc:        "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org>
Subject:   Re: ZFS on root booting broken somewhere after r270020
Message-ID:  <090135D4-8B1F-42B4-82FC-6FD2F1DBDDA8@icloud.com>
In-Reply-To: <4450778127F4407EB6566A0FE11CD651@multiplay.co.uk>
References:  <51AD1F36-1089-481F-8784-8BD8E6EF020F@icloud.com> <71DEB316-3CDD-4403-A397-BCE684725ABD@icloud.com> <25886C53-39C1-47A8-95F7-494FA6E7ABA2@icloud.com> <20140819071045.GS2737@kib.kiev.ua> <99FB0662-1954-4ECB-939B-06D0AA49C1A1@icloud.com> <20140819074643.GU2737@kib.kiev.ua> <FE64613E-B083-436C-8A08-13923ED88797@icloud.com> <7F008C560B48412AB66A1EBD9382DDAE@multiplay.co.uk> <CC276D59-F83C-4C78-BD9B-84040D3DE3E4@icloud.com> <9315C209-701A-49EF-85D3-ACCCD1513EC3@icloud.com> <959C54D2C8EB4AC8983DC1DA3CE042E3@multiplay.co.uk> <9F24DD48FBEA46C39F98DF600D46DA1A@multiplay.co.uk> <B4A16726-142D-458A-9B3A-153BDD579A63@icloud.com> <BAB9F50F-9D2C-435C-8035-659E2B412FC7@icloud.com> <4450778127F4407EB6566A0FE11CD651@multiplay.co.uk>

next in thread | previous in thread | raw e-mail | index | archive | help

> On 11.9.2014, at 4.25, Steven Hartland <killing@multiplay.co.uk> =
wrote:
>=20
> ----- Original Message ----- From: "Kimmo Paasiala" =
<kpaasial@icloud.com>
>=20
> snip...
>=20
>> Just a thought. Is my problem related to the use of GPT labeled =
partitions
>> in my pool configuration? Your testing shows just "raw" devices like =
ada0p3 etc.
>=20
> That "should" have no impact on anything, we disable gptids and =
diskid's as we
> don't like them adding an extra layer for lookups when admins are =
working with
> the machines.
>=20
>   Regards
>   Steve

I recreated the pool on the second disk as another single disk pool, =
performed zfs send -R =E2=80=A6 | zfs receive -F =E2=80=A6

It works now just fine with the kernel that didn=E2=80=99t work with old =
pool so there must have been something seriously broken with the old =
pool. I also noticed the old pool kept repeatedly restarting the =
resilver operations when I tried to expand it into a mirror.

Case closed for now.

-Kimmo





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?090135D4-8B1F-42B4-82FC-6FD2F1DBDDA8>