Date: Fri, 11 Jul 2008 17:57:37 -0700 From: Xin LI <delphij@delphij.net> To: duncan.young@pobox.com Cc: freebsd-current@freebsd.org Subject: Re: Boot from ZFS Message-ID: <48780181.2080905@delphij.net> In-Reply-To: <200807121043.10473.duncan.young@pobox.com> References: <4877A343.2010602@ibctech.ca> <20080711182430.GA76378@keltia.freenix.fr> <200807121043.10473.duncan.young@pobox.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Duncan Young wrote: | Be carefull, I've just had a 6 disk raidz array die. Complete failure which | required restore from backup (the controler card which had access to 4 of the | disks, lost one disk, then a second (at which point the machine paniced, Upon | reboot the raidz array was useless (Metadata corrupted)). I'm also getting | reasonably frequent machine lockups (panics) in the zfs code. I'm going to | start collecting crash dumps see if anyone can help in the next week or two. That's really unfortunate. Some sort of automated disk monitoring stuff would be essential for RAID, this includes RAID-Z. Did you used the whole disk dedicatedly for the pool, or (g)labeled before adding it into the zpool? Did 'zpool import -f' help? | I guess what I'm trying to say is, that you can still lose everything on an | entire pool, so backups are still essential, an a couple of smaller pools is | probably preferable to one big pool (restore time is less). zfs is not %100 | (yet?). The lack of any type of fsck still causes me concern. It's always true that backup is always important if data is valuable :) ~ The benefit having larger pool is that the administrator would have the ability to use larger disk space in one ZFS file system (which can not come cross zpool boundary), but it is recommended that when creating the zpool, we use smaller raid-z groups, e.g. don't use 48 disks within one raid-z group, a few disks (like 3-5) within one raid-z group would be fine. Regarding to fsck, 'zpool scrub' is pretty much like a fsck plus data integration check. It would be, however, almost impossible to recover data if zpool is completely corrupt according to some Sun sources, but my experience with bad disks within raid-z did not turned me into a unrecoverable state (yet). Cheers, - -- Xin LI <delphij@delphij.net> http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkh4AYEACgkQi+vbBBjt66A0FQCfVM/kpGQYJuNiUffxtsTgAgtJ lJIAnilKkCg1Tvf5JWd6aH9XyMjUfhBX =djMu -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48780181.2080905>