From owner-freebsd-scsi Tue Oct 12 17: 0: 3 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 6B95614A15 for ; Tue, 12 Oct 1999 16:59:57 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id JAA40430; Wed, 13 Oct 1999 09:29:50 +0930 (CST) Date: Wed, 13 Oct 1999 09:29:50 +0930 From: Greg Lehey To: Stefan Huerter Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: panic: vinvalbuf: dirty bufs Message-ID: <19991013092949.Q78191@freebie.lemis.com> References: <7Qhqy3MEoRB@subloch.medicusnet.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <7Qhqy3MEoRB@subloch.medicusnet.de> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tuesday, 12 October 1999 at 9:10:00 +0200, Stefan Huerter wrote: > Guckux > > Running FreeBSD 3.3-STABLE > > from dmesg: > da2 at ahc0 bus 0 target 1 lun 0 > da2: Fixed Direct Access SCSI-2 device > da2: 8.064MB/s transfers (8.064MHz, offset 15), Tagged Queueing Enabled > da2: 1908MB (3907911 512 byte sectors: 64H 32S/T 1908C) > > I've recognized with FreeBSD 3.1 that this drive has problems with > taggings, so I reduced them. > > I encounterd with FB 3.2 problems with this drive. Upgraded to FB 3.3 I > checked it once more and get more problems. It is controlled from a > Adaptec 2940, I make a low level format with the Adaptec-Bios and check 3 > times via "verify disk media" with no problems. > When I make a "newfs -i 8192" (with tagging disabled through camcontrol > command) there will be a few superblocks written out, then newfs will stop > (no screen-output anymore), the drive scratches a little bit and then I > get following: > panic: vinvalbuf: dirty bufs > > any chance to get it working back? or is it really damaged? This panic happens when a device is being closed and for some reason the open buffers can't be written to disk. If it happens in the middle of newfs, it suggests that the drive had an I/O error of some kind which prevented data from being written during close. A dump would be really helpful. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message