From owner-freebsd-current Thu May 18 15: 8:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 3B97F37BB23 for ; Thu, 18 May 2000 15:08:25 -0700 (PDT) (envelope-from ticso@cicely5.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.9.3/8.9.3) with ESMTP id XAA27688; Thu, 18 May 2000 23:57:32 +0200 (MET DST) Received: from cicely5.cicely.de (cicely5.cicely.de [10.1.5.7]) by mail.cicely.de (8.9.3/8.9.0) with ESMTP id AAA21786; Fri, 19 May 2000 00:02:01 +0200 (CEST) Received: (from ticso@localhost) by cicely5.cicely.de (8.9.3/8.9.2) id AAA30659; Fri, 19 May 2000 00:02:00 +0200 (CEST) (envelope-from ticso) Date: Fri, 19 May 2000 00:01:59 +0200 From: Bernd Walter To: "Niels Chr. Bank-Pedersen" Cc: Bernd Walter , freebsd-current@FreeBSD.ORG Subject: Re: panic: ffs_valloc: dup alloc Message-ID: <20000519000159.B30272@cicely5.cicely.de> References: <20000518161343.G26090@bank-pedersen.dk> <20000518232151.A30272@cicely5.cicely.de> <20000518234358.B28600@bank-pedersen.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000518234358.B28600@bank-pedersen.dk>; from ncbp@bank-pedersen.dk on Thu, May 18, 2000 at 11:43:58PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, May 18, 2000 at 11:43:58PM +0200, Niels Chr. Bank-Pedersen wrote: > On Thu, May 18, 2000 at 11:21:51PM +0200, Bernd Walter wrote: > > Does vinum list saying that one subdisk of your R5 volume is down? > > 5 subdisks: > S raid5.p0.s0 State: up PO: 0 B Size: 4133 MB > S raid5.p0.s1 State: up PO: 768 kB Size: 4133 MB > S raid5.p0.s2 State: up PO: 1536 kB Size: 4133 MB > S raid5.p0.s3 State: up PO: 2304 kB Size: 4133 MB > S raid5.p0.s4 State: up PO: 3072 kB Size: 4133 MB > > - But since my first attempt to initialize the plex crashed the > box while only da5se1 was missing, I did a "verify media" from > the SCSI ctrl. BIOS, and did find errors. They were all successfully > remapped, though. I thought about a parity corrpution bug that there was in history. But as all drives are up and they are freshly initialized there are 2 arguments why your problems should be different. Maybe one drive crashed and the system paniced before vinum was able to update the state database on the drives. Did you saw anything unusual on the console before the panic message? > > Are you using softupdates? > > Yup. I am unable to try without SU right now (well, I could, but if it > doesnt work, my foot will be blown of), but I'll try that later when I > get home. It's only of interesst if it was/is enabled on the volume in question and not if it is compiled into the kernel. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message