Date: Sat, 19 Feb 2011 14:44:38 +0000 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Daniel Staal <DStaal@usa.net> Cc: freebsd-questions@freebsd.org Subject: Re: ZFS-only booting on FreeBSD Message-ID: <4D5FD756.5020306@infracaninophile.co.uk> In-Reply-To: <F2D539249AB2457E49ED2013@mac-pro.magehandbook.com> References: <97405dd7ad34c6cbecebfdda327d1e83.squirrel@www.magehandbook.com> <4D5FB121.6090102@infracaninophile.co.uk> <F2D539249AB2457E49ED2013@mac-pro.magehandbook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig94A981D5C8C4009DD44EE330
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
On 19/02/2011 13:18, Daniel Staal wrote:
>> Why wouldn't it be? The configuration in the Wiki article sets aside =
a
>> small freebsd-boot partition on each drive, and the instructions tell
>> you to install boot blocks as part of that partitioning process. You
>> would have to repeat those steps when you install your replacement dri=
ve
>> before you added the new disk into your zpool.
>>
>> So long as the BIOS can read the bootcode from one or other drives, an=
d
>> can then access /boot/zfs/zpool.cache to learn about what zpools you
>> have, then the system should boot.
>=20
> So, assuming a forgetful sysadmin (or someone who is new didn't know
> about the setup in the first place) is that a yes or a no for the
> one-drive replaced case?
Umm... a sufficiently forgetful sysadmin can break *anything*. This
isn't really a fair test: forgetting to write the boot blocks onto a
disk could similarly render a UFS based system unbootable. That's why
scripting this sort of stuff is a really good idea. Any new sysadmin
should of course be referred to the copious and accurate documentation
detailing exactly the steps needed to replace a drive...
ZFS is definitely advantageous in this respect, because the sysadmin has
to do fewer steps to repair a failed drive, so there's less opportunity
for anything to be missed out or got wrong.
The best solution in this respect is one where you can simply unplug the
dead drive and plug in the replacement. You can do that with many
hardware RAID systems, but you're going to have to pay a premium price
for them. Also, you loose out on the general day-to-day benefits of
using ZFS.
> It definitely is a 'no' for the all-drives replaced case, as I
> suspected: You would need to have repeated the partitioning manually.=20
> (And not letting ZFS handle it.)
Oh, assuming your sysadmins consistently fail to replace the drives
correctly, then depending on your BIOS you can be in deep do-do as far
as rebooting goes rather sooner than that.
> If a single disk failure in the zpool can render the machine
> unbootable, it's better yet to have a dedicated bootloader drive
If a single disk failure renders your system unbootable, then you're
doing it wrong. ZFS-root systems should certainly reboot if zfs can
still assemble the root pool -- so with one disk failed for RAIDZ1, or
two for RAIDZ2 or up to half the drives for mirror.
If this failure to correctly replace broken drives is going to be a
significant problem in your environment, then I guess you're going to
have to define appropriate processes. You might say that in the event
of a hard drive being replaced, it is mandatory to book some planned
downtime at the next convenient point, and do a test reboot + apply any
remedial work needed. If your system design is such that you can't take
any one machine down for maintenance, even with advance warning then
you've got more important problems to solve before you worry about using
ZFS or not.
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
--------------enig94A981D5C8C4009DD44EE330
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.16 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk1f11YACgkQ8Mjk52CukIxv2wCgiCWDxArXvOor95ED9jiWpG5X
9UwAoJEl1y4VONo2N/drFhF9un2FXzzC
=Ceh1
-----END PGP SIGNATURE-----
--------------enig94A981D5C8C4009DD44EE330--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D5FD756.5020306>