From owner-freebsd-current Tue Mar 16 12:15:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 1CC0514D78 for ; Tue, 16 Mar 1999 12:15:20 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id NAA27542; Tue, 16 Mar 1999 13:14:52 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199903162014.NAA27542@panzer.plutotech.com> Subject: Re: repeated ufs_dirbad() panics on 4.0-c In-Reply-To: <19990316223637.A31464@demos.su> from "Mikhail A. Sokolov" at "Mar 16, 1999 10:36:38 pm" To: mishania@demos.net (Mikhail A. Sokolov) Date: Tue, 16 Mar 1999 13:14:52 -0700 (MST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mikhail A. Sokolov wrote... > Hello, > > we're experiencing repeated 4.0-C (as of today, something around 12:00 > GMT, 1999-03-16) ufs_dirbad() panics, which are the > following (below), which usually occur when squid is running. The box > doesn't have ccd, nor vinum nor anything fancy in it's config, no SMP either. > Squid's spool is hardware (IFT3102) RAID1, 2x9gb (i.e. 4 disks): > /var/crash# gdb -k kernel.1 vmcore.1 > IdlePTD 2682880 > initial pcb at 21c7b8 > panicstr: ufs_dirbad: bad dir > panic messages: > --- > panic: ufs_dirbad: bad dir I have no idea why you're getting a panic, but I do have a question... > syncing disks... 134 63 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 giving up > (da1:ahc1:0:1:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 > (da1:ahc1:0:1:0): ILLEGAL REQUEST asc:20,0 > (da1:ahc1:0:1:0): Invalid command operation code > (da2:ahc1:0:2:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 > (da2:ahc1:0:2:0): ILLEGAL REQUEST asc:20,0 > (da2:ahc1:0:2:0): Invalid command operation code > (da3:ahc1:0:3:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 > (da3:ahc1:0:3:0): ILLEGAL REQUEST asc:20,0 > (da3:ahc1:0:3:0): Invalid command operation code Are you *sure* you're running -current as of today? Justin put code in to silence Illegal request error messages from the sync cache command. What revision of scsi_da.c do you have, and has it been modified? Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message