From owner-freebsd-stable@FreeBSD.ORG Mon Jul 30 05:33:43 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 86CBF106566C; Mon, 30 Jul 2012 05:33:43 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from elf.hq.norma.perm.ru (unknown [IPv6:2001:470:1f09:14c0::2]) by mx1.freebsd.org (Postfix) with ESMTP id 942758FC08; Mon, 30 Jul 2012 05:33:42 +0000 (UTC) Received: from bsdrookie.norma.com. ([IPv6:fd00::7fc]) by elf.hq.norma.perm.ru (8.14.5/8.14.5) with ESMTP id q6U5XeQA033228 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 30 Jul 2012 11:33:40 +0600 (YEKT) (envelope-from emz@norma.perm.ru) Message-ID: <50161CB4.3020309@norma.perm.ru> Date: Mon, 30 Jul 2012 11:33:40 +0600 From: "Eugene M. Zheganin" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120727 Thunderbird/14.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org, mav@freebsd.org References: <501615EA.7020402@norma.perm.ru> In-Reply-To: <501615EA.7020402@norma.perm.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (elf.hq.norma.perm.ru [IPv6:fd00::30a]); Mon, 30 Jul 2012 11:33:40 +0600 (YEKT) X-Spam-Status: No hits=-97.8 bayes=0.5 testhits RDNS_NONE=1.274, SPF_SOFTFAIL=0.972,USER_IN_WHITELIST=-100 autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on elf.hq.norma.perm.ru Cc: Subject: Re: GEOM_RAID in GENERIC 9.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jul 2012 05:33:43 -0000 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.