GEOM_RAID in GENERIC 9.1
Eugene M. Zheganin
emz at norma.perm.ru
Mon Jul 30 05:33:43 UTC 2012
Hi.
On 30.07.2012 11:04, Eugene M. Zheganin wrote:
>
> I am aware about how this thing works and what it does. However, every
> time I upgrade new server I got hit by it again and again, simply
> forgetting to remove it from the kernel's config.
>
> I'm afraid this thing will hit lots of FreeBSD installations after the
> release; it may be easily removed but still it will poison the life of
> many engineers and I really think it's a bomb, and should be removed
> from GENERIC.
>
Okay, I feel like I need to clarify this, as some decent guys pointed me
out that I'm very unclear and even rude (sorry for that, that's
unintentional).
GEOM_RAID was inserted instead of ataraid, but ataraid wasn't messing
with zpooled disks: with GEOM_RAID the kernel takes both (in case of
mirrored pool) providers, and mountroot just fails, as it sees no zfs pool.
Plus, it's even more. This time I have "disabled" the raid in it's
"BIOS" before installing FreeBSD. After mountroot failed, I booted 9.0-R
from usb flash, trying to avoid any surgery with kernel files, like
manual install from another machine. I was curious if I will be able to
resolve this issue using base utilities. So, I loaded geom_raid via
'graid load', kernel said like 'Doh... I have ada0/ada1 spare disks',
then I tried to remove the softraid label remains with 'graid remove' -
and it failed, because there's no array at all, only "spares". So, the
'graid status' is empty, 'graid list' is empty' and it's obvious that
some surgery is needed.
And I'm not disappointed that it's happened to me, no, because I know
how to resolve this.
But the thing that I'm really afraid of is that this default option will
hit the less experienced engineers.
Eugene.
More information about the freebsd-stable
mailing list