From owner-freebsd-stable@FreeBSD.ORG  Sun Nov  7 18:45:31 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 3ACF016A4CE
	for <freebsd-stable@freebsd.org>;
	Sun,  7 Nov 2004 18:45:31 +0000 (GMT)
Received: from mta9.adelphia.net (mta9.adelphia.net [68.168.78.199])
	by mx1.FreeBSD.org (Postfix) with ESMTP id BDFE343D4C
	for <freebsd-stable@freebsd.org>;
	Sun,  7 Nov 2004 18:45:30 +0000 (GMT)
	(envelope-from security@jim-liesl.org)
Received: from smtp.jim-liesl.org ([68.71.52.28]) by mta9.adelphia.net
          (InterMail vM.6.01.03.02 201-2131-111-104-20040324) with ESMTP
          id <20041107184530.GZQX4778.mta9.adelphia.net@smtp.jim-liesl.org>;
          Sun, 7 Nov 2004 13:45:30 -0500
Received: from [192.168.1.101] (unknown [192.168.1.101])
	by smtp.jim-liesl.org (Postfix) with ESMTP
	id 13F54152B2; Sun,  7 Nov 2004 11:45:29 -0700 (MST)
From: secmgr <security@jim-liesl.org>
To: Joe Koberg <joe@osoft.us>
In-Reply-To: <418E4F9C.4070109@osoft.us>
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>  <418E4F9C.4070109@osoft.us>
Content-Type: text/plain
Organization: 
Message-Id: <1099853128.4420.12.camel@emperor>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) 
Date: 07 Nov 2004 11:45:28 -0700
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 18:45:31 -0000

It did, but can you tell me anywhere in the docs it says to do that?  Or
maybe that vinum should sense that and throw some error rather than just
blindly corrupting itself.

jim
On Sun, 2004-11-07 at 09:38, Joe Koberg wrote:
> 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
> 
>