Date: Thu, 12 Dec 2013 23:16:51 +0000 From: Florent Peterschmitt <florent@peterschmitt.fr> To: Artem Belevich <art@freebsd.org> Cc: freebsd-fs <freebsd-fs@freebsd.org>, freebsd-stable stable <freebsd-stable@freebsd.org>, Andriy Gapon <avg@freebsd.org> Subject: Re: 10.0-BETA4 (upgraded from 9.2-RELEASE) zpool upgrade -> boot failure Message-ID: <52AA43E3.7020706@peterschmitt.fr> In-Reply-To: <CAFqOu6jUqy6Y4AD3D32ZPsVS59GJMWAH286bne6T3roMK19Ofw@mail.gmail.com> References: <52A6EB67.3000103@peterschmitt.fr> <52A99917.2050200@FreeBSD.org> <52A9AA45.2000907@peterschmitt.fr> <52A9ABEF.8080509@FreeBSD.org> <CAFqOu6g1ih3Z70Z4gip0BowmSAJ6dE4X8WgR0au1Rx5udmtZXw@mail.gmail.com> <52AA26DA.30809@peterschmitt.fr> <CAFqOu6jUqy6Y4AD3D32ZPsVS59GJMWAH286bne6T3roMK19Ofw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--tVSpilNHrmUUa2nDwWtXcodpOMPvi4kfF
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Le 12/12/2013 22:04, Artem Belevich a =E9crit :
> On Thu, Dec 12, 2013 at 1:12 PM, Florent Peterschmitt
> <florent@peterschmitt.fr> wrote:
>>> do "zdb -l /dev/ada0" (and all other slices on ada0) and check
>>> whether it reports anything unexpected.
>>>
>>> --Artem
>>
>> rescue-bsd# zdb -l /dev/ada0
>> --------------------------------------------
>> LABEL 0
>> --------------------------------------------
>> failed to unpack label 0
>> --------------------------------------------
>> LABEL 1
>> --------------------------------------------
>> failed to unpack label 1
>> --------------------------------------------
>> LABEL 2
>> --------------------------------------------
>> failed to unpack label 2
>> --------------------------------------------
>> LABEL 3
>> --------------------------------------------
>> failed to unpack label 3
>>
>>
>> Well=85 this sounds bad, right?
>=20
> This looks the way it's supposed to -- no unwanted ZFS pool info is fou=
nd.
>=20
> Now repeat that for all ada0p? and make sure only the slice that's
> part of your pool shows ZFS labels and only for one pool.
>=20
> Think a bit about how bootloader figures out how your pool is built.
> All it has access to is a raw disk and partition table. So in order to
> find the pool it probes raw disk and all partitions trying to find ZFS
> labels and then uses info in those labels to figure out pool
> configuration. If bootloader finds stale ZFS labels left from a
> previous use of the disk in some other pool, it would potentially mess
> up detection of your real boot pool.
>=20
> --Artem
>=20
rescue-bsd# zdb -l /dev/ada0p1
--------------------------------------------
LABEL 0
--------------------------------------------
failed to read label 0
--------------------------------------------
LABEL 1
--------------------------------------------
failed to read label 1
--------------------------------------------
LABEL 2
--------------------------------------------
failed to read label 2
--------------------------------------------
LABEL 3
--------------------------------------------
failed to read label 3
rescue-bsd# zdb -l /dev/ada0p2
--------------------------------------------
LABEL 0
--------------------------------------------
failed to unpack label 0
--------------------------------------------
LABEL 1
--------------------------------------------
failed to unpack label 1
--------------------------------------------
LABEL 2
--------------------------------------------
failed to unpack label 2
--------------------------------------------
LABEL 3
--------------------------------------------
failed to unpack label 3
rescue-bsd# zdb -l /dev/ada0p3
--------------------------------------------
LABEL 0
--------------------------------------------
version: 5000
name: 'tank'
state: 0
txg: 1248416
pool_guid: 14109252772653171024
hostid: 1349238423
hostname: 'rescue-bsd.ovh.net'
top_guid: 8826573031965252809
guid: 8826573031965252809
vdev_children: 1
vdev_tree:
type: 'disk'
id: 0
guid: 8826573031965252809
path: '/dev/gpt/zfs-root'
phys_path: '/dev/gpt/zfs-root'
whole_disk: 1
metaslab_array: 30
metaslab_shift: 32
ashift: 9
asize: 493660405760
is_log: 0
create_txg: 4
features_for_read:
--------------------------------------------
LABEL 1
--------------------------------------------
version: 5000
name: 'tank'
state: 0
txg: 1248416
pool_guid: 14109252772653171024
hostid: 1349238423
hostname: 'rescue-bsd.ovh.net'
top_guid: 8826573031965252809
guid: 8826573031965252809
vdev_children: 1
vdev_tree:
type: 'disk'
id: 0
guid: 8826573031965252809
path: '/dev/gpt/zfs-root'
phys_path: '/dev/gpt/zfs-root'
whole_disk: 1
metaslab_array: 30
metaslab_shift: 32
ashift: 9
asize: 493660405760
is_log: 0
create_txg: 4
features_for_read:
--------------------------------------------
LABEL 2
--------------------------------------------
version: 5000
name: 'tank'
state: 0
txg: 1248416
pool_guid: 14109252772653171024
hostid: 1349238423
hostname: 'rescue-bsd.ovh.net'
top_guid: 8826573031965252809
guid: 8826573031965252809
vdev_children: 1
vdev_tree:
type: 'disk'
id: 0
guid: 8826573031965252809
path: '/dev/gpt/zfs-root'
phys_path: '/dev/gpt/zfs-root'
whole_disk: 1
metaslab_array: 30
metaslab_shift: 32
ashift: 9
asize: 493660405760
is_log: 0
create_txg: 4
features_for_read:
--------------------------------------------
LABEL 3
--------------------------------------------
version: 5000
name: 'tank'
state: 0
txg: 1248416
pool_guid: 14109252772653171024
hostid: 1349238423
hostname: 'rescue-bsd.ovh.net'
top_guid: 8826573031965252809
guid: 8826573031965252809
vdev_children: 1
vdev_tree:
type: 'disk'
id: 0
guid: 8826573031965252809
path: '/dev/gpt/zfs-root'
phys_path: '/dev/gpt/zfs-root'
whole_disk: 1
metaslab_array: 30
metaslab_shift: 32
ashift: 9
asize: 493660405760
is_log: 0
create_txg: 4
features_for_read:
Since freebsd-zfs is installed on ada0p3, it's normal to get that. Then,
what can you say about that?
--=20
Florent Peterschmitt | Please:
florent@peterschmitt.fr | * Avoid HTML/RTF in E-mail.
+33 (0)6 64 33 97 92 | * Send PDF for documents.
http://florent.peterschmitt.fr | * Trim your quotations. Really.
Proudly powered by Open Source | Thank you :)
--tVSpilNHrmUUa2nDwWtXcodpOMPvi4kfF
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJSqkPjAAoJEFr01BkajbiBaukP/3TH5uZf1n+dyUChBkkWM4kt
fiM8b/y7DOGwBFQQu2HWTvc5rthXkKB8vYyg3L32NRB+ntlA8Th8LrC0EeunRAcq
k2NI8CNFIml4EBklQy+dtMpcSs4xwPnJLUkes8t0icQcDr7340df0Nr516f6QayS
v1sKWfEgAt8yZbkt+fvSJCz20CCmGacLjI0p8K/lhBL37JSj5u/eu+sD7tIPjleS
+0YVq60B0mFUMYyoTMH/jmQZZr2VJYtqfIRMFrYl2xSYEKfDbSoUkuTuAGzEaHdi
cegc4tOYt+IgvaiWNMomxDj4/coh5d3LNjfXHQSikYmAVLqPDLJHZ2s/NpPQ+FaH
OyXYxw+tF/7d/lFemt3Qh7gwwcEnVXoww8QEkmCLk/9i3k/NrcDTXNdZWG6KWlZh
JFCH101v/8ShQPcjndxTtM4PqPK9eQTZtbyVOP0XpRz6AveT7336bM2/g8Xl3BJW
UCK4CxUFnQfFl3iskW5qfmZZprcvOMdV/1Y4kLDhwa7/fd3OpKUmCOTqlLLS3xq/
viwumRg7btJzI0A+3BqQdEA+tpYYdzCcAICnJ3MUu4sC1tEU9KdNITrIWaAw6aaW
ForOZIgacZBiBw1CiTE4DK0+JAKwr2pW7+XnWMLKMitja7XQXtCtDA4I4IxJItt4
fWzopUQbwuEZdHcN4Jy7
=RQ4a
-----END PGP SIGNATURE-----
--tVSpilNHrmUUa2nDwWtXcodpOMPvi4kfF--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52AA43E3.7020706>