From owner-freebsd-stable@FreeBSD.ORG Fri Oct 22 14:00:49 2004 Return-Path: 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 C8C5D16A4CE for ; Fri, 22 Oct 2004 14:00:49 +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 D105943D45 for ; Fri, 22 Oct 2004 14:00:34 +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 C4B17D4BA; Fri, 22 Oct 2004 09:00:31 -0500 (CDT) Message-ID: <4179128E.3050704@osoft.us> Date: Fri, 22 Oct 2004 09:00:46 -0500 From: Joe Koberg User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626) X-Accept-Language: en-us, en MIME-Version: 1.0 To: secmgr References: <41783571.5070204@jim-liesl.org> In-Reply-To: <41783571.5070204@jim-liesl.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org Subject: Re: newfs -v on vinum raid5 panics system (4.10-p3 RELEASE) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Oct 2004 14:00:50 -0000 secmgr wrote: > partition the same size as the slice (c=h), and then let the subdisks > use the entire partition (len 0), the raid set is corrupted every time > after initializing. This usually leads to a kernel panic during > newfs. If I leave some amount free, (ie the subdisk only uses 8000mb > of a 8675mb drive) no problem. If i'm RTFM'ing correctly, it looks > like it should reserve 132kb per drive. I guess I assumed that would > be automagically reserved, or if it's supposed to be, it's getting > walked on. > > Next, I disklabel each drive (they're all identical) > # /dev/da0s1c: > # size offset fstype [fsize bsize bps/cpg] > c: 17767827 0 unused 0 0 # (Cyl. 0 - > 1105*) > h: 17767827 0 vinum # (Cyl. 0 - > 1105*) > I alway leave 64 sectors free at the beginning of the disk: h: 17767763 64 vinum # (Cyl. 0 - 1105*) I think this is where the partition tables live, you are probably overwriting them when vinum writes its metadata. I think a normal UFS filesystem will leave 64 sectors of slack space at the beginning of the partition, but vinum may not. I may also be totally wrong. Joe Koberg joe at osoft dot us