Date: Sat, 02 Oct 2010 16:13:28 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: =?UTF-8?B?UGV0ZXIgQW5rZXJzdMOlbA==?= <peter@pean.org> Cc: "Marat N.Afanasyev" <amarat@ksu.ru>, stable@freebsd.org Subject: Re: device names changes for adX. Message-ID: <4CA74C18.2020405@infracaninophile.co.uk> In-Reply-To: <D05E5388-C330-47D8-A9F1-2A1C65D11B3E@pean.org> References: <1C68D21A-9539-473D-AEDB-9A8CCE4956F1@pean.org> <4CA73215.9030908@ksu.ru> <D05E5388-C330-47D8-A9F1-2A1C65D11B3E@pean.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig6F1BD6F6B75A7669257774CC
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
On 02/10/2010 15:29:49, Peter Ankerst=C3=A5l wrote:
>> Peter Ankerst=C3=A5l wrote:
>>> When I installed FreeBSD 8.1-RELEASE (freebsd-update) the adX devices=
changed index number and
>>> the machine obviously didnt boot. Due to this I hesitate to install 8=
=2E1 on my servers remote. How do I know
>>> if and to what the devices will change?
>> label your filesystems and mount them by label rather than by device n=
ame. see
>>
>> man glabel
> Thanks, I may try that. But how will this affect ZFS raidz set up to us=
e ad-drives?
>=20
> Like this:
>=20
> tank ONLINE 0 0 0
> raidz1 ONLINE 0 0 0
> ad10s2 ONLINE 0 0 0
> ad12 ONLINE 0 0 0
> ad14 ONLINE 0 0 0
> ad16 ONLINE 0 0 0
It actually shouldn't matter. ZFS writes metadata about the zpools,
zdevs etc. it knows about onto the drives, and if it can read the drive
and see the metadata, it can reconstruct itself. You can take disks out
of a ZFS setup, shuffle them, stick them back into the wrong slots, and
ZFS will still work. Similarly, you can use glabel to name the disks,
and switch to using that, and everything should still work.
In fact, if you glabel the disks while ZFS is still active, it should
instantly recognise all the new names and update the 'zpool status'
output on the fly. Actually, that last is probably the right way to do
things -- you'll update the zpool.cache that way, which means that ZFS
will come up without any remedial action after reboot.
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matthew@infracaninophile.co.uk Kent, CT11 9PW
--------------enig6F1BD6F6B75A7669257774CC
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkynTCAACgkQ8Mjk52CukIxIXQCfZjARgmx5JqyXsWTg+t+zCg9C
VBcAoIh+/LFFRRLqFe+EID8Y9gIs5Abc
=hsgs
-----END PGP SIGNATURE-----
--------------enig6F1BD6F6B75A7669257774CC--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4CA74C18.2020405>