From owner-freebsd-stable@FreeBSD.ORG  Sun Nov  7 16:38:00 2004
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 0E84316A4CE
	for <freebsd-stable@freebsd.org>;
	Sun,  7 Nov 2004 16:38:00 +0000 (GMT)
Received: from diligence.flag.rootnode.com
	(adsl-65-67-81-98.dsl.ltrkar.swbell.net [65.67.81.98])
	by mx1.FreeBSD.org (Postfix) with ESMTP id AB1F243D3F
	for <freebsd-stable@freebsd.org>;
	Sun,  7 Nov 2004 16:37:59 +0000 (GMT)	(envelope-from joe@osoft.us)
Received: from [10.0.1.105] (coherence.flag.rootnode.com [10.0.1.105])
	by diligence.flag.rootnode.com (Postfix) with ESMTP
	id E1E28D4BA; Sun,  7 Nov 2004 10:37:58 -0600 (CST)
Message-ID: <418E4F9C.4070109@osoft.us>
Date: Sun, 07 Nov 2004 10:38:52 -0600
From: Joe Koberg <joe@osoft.us>
User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: secmgr <security@jim-liesl.org>
References: <02f201c4ba91$f9f95db0$33017f80@psique>
	<20041103031316.A95136@titus.hanley.stade.co.uk>
	<41893F4D.6090702@jim-liesl.org>  <200411061309.11883.msch@snafu.de>
	<1099805316.4420.2.camel@emperor>
In-Reply-To: <1099805316.4420.2.camel@emperor>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
cc: msch@snafu.de
cc: freebsd-stable@freebsd.org
Subject: Re: freebsd 5.3 have any problem with vinum ?
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Nov 2004 16:38:00 -0000

secmgr wrote:


>No, I mean self corrupting raid5 sets during initialization.  Discussed
>about 2-3 weeks ago.
>  
>
In the following message you seemed to claim that adding 64 sectors of 
slack to the
beginning of the vinum partition fixed this problem, as I suggested. Did 
that fix it or not?


> The reason is empirically derived.  When I created a 7 disk raid 5 set 
> using "len 0" or all the space available, the raid set would be 
> corrupt after initializing.  Every time.  When I reserved back  that 
> extra space, no corruption.
> (freebsd 4.10-p3)  There was a thread on this a few days ago.
>
> jim 



Joe Koberg
joe at osoft dot us