From owner-freebsd-geom@FreeBSD.ORG Mon Aug 13 20:40:39 2007 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E254E16A41A; Mon, 13 Aug 2007 20:40:39 +0000 (UTC) (envelope-from lulf@stud.ntnu.no) Received: from signal.itea.ntnu.no (signal.itea.ntnu.no [129.241.190.231]) by mx1.freebsd.org (Postfix) with ESMTP id 9A1B013C461; Mon, 13 Aug 2007 20:40:39 +0000 (UTC) (envelope-from lulf@stud.ntnu.no) Received: from localhost (localhost [127.0.0.1]) by signal.itea.ntnu.no (Postfix) with ESMTP id A49AD34A20; Mon, 13 Aug 2007 22:40:37 +0200 (CEST) Received: from gaupe.stud.ntnu.no (gaupe.stud.ntnu.no [129.241.56.184]) by signal.itea.ntnu.no (Postfix) with ESMTP; Mon, 13 Aug 2007 22:40:35 +0200 (CEST) Received: by gaupe.stud.ntnu.no (Postfix, from userid 2312) id DB455D0046; Mon, 13 Aug 2007 22:40:35 +0200 (CEST) Date: Mon, 13 Aug 2007 22:40:35 +0200 From: Ulf Lilleengen To: freebsd-current@freebsd.org, freebsd-geom@freebsd.org, freebsd-arch@freebsd.org Message-ID: <20070813204035.GA5338@stud.ntnu.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.9i X-Content-Scanned: with sophos and spamassassin at mailgw.ntnu.no. Cc: le@FreeBSD.org Subject: Testers wanted: Gvinum patches of SoC 2007 work X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Aug 2007 20:40:40 -0000 Hi, It's here! The new and hopefully better gvinum patch. This is perhaps my final patch of the work I've done during GSoC 2007 (the patch will be updated when I fix a bug). This doesn't mean I'll stop work on gvinum, but rather that I'm not adding more features until this gets into the tree. But, for this to get into the tree, I need people to test it. _ALL_ reports on how it works is good. So, what should you test? * Plain normal use. * Mirror synchronization, rebuild if raid-5 arrays, growing of raid-5 arrays etc. These should work, and probably is the most tested, but some weird combinations that I have not forseen might show itself. * Try weird combinations to check if it crashes. * Test mirror, concat, stripe and raid5 commands. * If there are any issues with the usability aspect. E.g. if the information gvinum gives you is good enough for you to understand what it's doing, if one way to do things seems unnatural to you etc. I'd like to hear all of this, no matter how bikshedish it might sound, it might be something that have been overlooked. These things are hard to test for the people that have been developing it, since we know how it "should" be used. Before you head on, beware that the new gvinum does not give messages back to the userland gvinum (so you won't get them into your terminal). This is because it's not very simple to do with the new event system. !! This means you'll have to look after messages in /var/log/messages !! And thanks to people for comments and help that I've been getting during the summer. -- Ulf Lilleengen