From owner-cvs-src@FreeBSD.ORG Wed Oct 20 17:16:08 2004 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9331716A4CE; Wed, 20 Oct 2004 17:16:08 +0000 (GMT) Received: from gw.Awfulhak.org (awfulhak.demon.co.uk [80.177.173.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D19443D3F; Wed, 20 Oct 2004 17:16:07 +0000 (GMT) (envelope-from brian@Awfulhak.org) Received: from dev.lan.Awfulhak.org (brian@dev.lan.Awfulhak.org [172.16.0.5]) by gw.Awfulhak.org (8.13.1/8.13.1) with SMTP id i9KHFde2010304; Wed, 20 Oct 2004 18:15:39 +0100 (BST) (envelope-from brian@Awfulhak.org) Date: Wed, 20 Oct 2004 18:15:49 +0100 From: Brian Somers To: Pawel Jakub Dawidek Message-ID: <20041020181549.1cbc2bd3@dev.lan.Awfulhak.org> In-Reply-To: <200410150611.i9F6BSRd066269@repoman.freebsd.org> References: <200410150611.i9F6BSRd066269@repoman.freebsd.org> X-Mailer: Sylpheed-Claws 0.9.12b (GTK+ 1.2.10; i386-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.0.0 X-Spam-Checker-Version: SpamAssassin 3.0.0 (2004-09-13) on gw.lan.Awfulhak.org cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/geom/raid3 g_raid3.c g_raid3.h X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Oct 2004 17:16:08 -0000 On Fri, 15 Oct 2004 06:11:28 +0000 (UTC), Pawel Jakub Dawidek wrote: > pjd 2004-10-15 06:11:28 UTC > > FreeBSD src repository > > Modified files: (Branch: RELENG_5) > sys/geom/raid3 g_raid3.c g_raid3.h > Log: > - There is no need to skip providers with 0 sectorsize in taste routine > anymore. Does this apply for raid5 too? I'm getting all sorts of zero sector size errors with a machine upgraded from RELENG_4 - but depending on when I bring vinum up! If I try to boot with vinum enabled, I get a dangling vnode panic. If I try to boot without vinum and have a vinum.sh startup that does a vinum start and a mount, I get a wrong sectorsize error and lose one of the six disks (ending up in degraded mode). The only way to get things up is to boot -s, ``fsck -p'', ``vinum start'', then continue to multi-user. -- Brian Don't _EVER_ lose your sense of humour !