From owner-freebsd-fs Sun Jun 9 0:46:29 2002 Delivered-To: freebsd-fs@freebsd.org Received: from prometheus.vh.laserfence.net (prometheus.laserfence.net [196.44.73.116]) by hub.freebsd.org (Postfix) with ESMTP id 3AE2C37B405 for ; Sun, 9 Jun 2002 00:46:14 -0700 (PDT) Received: from phoenix.vh.laserfence.net ([192.168.0.10]) by prometheus.vh.laserfence.net with esmtp (Exim 3.34 #1) id 17GxOk-0002C3-00 for freebsd-fs@freebsd.org; Sun, 09 Jun 2002 09:46:02 +0200 Date: Sun, 9 Jun 2002 09:46:02 +0200 (SAST) From: Willie Viljoen X-X-Sender: will@phoenix.vh.laserfence.net To: freebsd-fs@freebsd.org Subject: Strange filesystem problem revisited... Message-ID: <20020609094005.I210-100000@phoenix.vh.laserfence.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I've got another rather desturbing problem with the ata/ufs code... Awhile back I submitted several bug reports regarding mysterious kernel panics early in the morning, and the system coming back up unable to reboot due to softupdate inconsitancies almost everywhere on the drive... For months, this problem seemed to dissapear, then yesterday, I reinstalled my windows partition (used mostly for games, so, used very seldom) This morning, when I got to the machine, the problem had returned. Could this have anything to do with the mounted FAT32 file systems? If so, why does it not appear when those FAT32s are mounted, but have nothing on them? I also enabled power management for the hard drive yesterday, could this be it? The drive is a Seagate ST340810A, the controller is a PCI ATA, integrated into an Asus P3V133, identified only as a VIA 82C596. The machine actually output one last message in the logs before its first reboot attempt: Jun 9 03:01:14 phoenix /kernel: dscheck(#ad/0x20007): negative b_blkno -1061109568 I'd really apreciate it if anyone could get me some help getting this to stop. I've tried all the handbook and mailing list bugfixes (turning off write behind, tuning my BIOS parameters manually to my drive specifications, etc) all to no avail. Will -- Willie Viljoen Private IT Consultant 214 Paul Kruger Avenue Universitas Bloemfontein 9321 South Africa +27 51 522 15 60, a/h +27 51 522 44 36 +27 82 404 03 27 will@laserfence.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message