From owner-freebsd-current Tue Sep 1 18:22:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05943 for freebsd-current-outgoing; Tue, 1 Sep 1998 18:22:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA05935 for ; Tue, 1 Sep 1998 18:22:08 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id SAA29132; Tue, 1 Sep 1998 18:21:07 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp02.primenet.com, id smtpd029119; Tue Sep 1 18:21:03 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id SAA12528; Tue, 1 Sep 1998 18:21:01 -0700 (MST) From: Terry Lambert Message-Id: <199809020121.SAA12528@usr01.primenet.com> Subject: Re: What the fsck is going on here (disk space vanishing)? To: rock@cs.uni-sb.de (D. Rock) Date: Wed, 2 Sep 1998 01:21:01 +0000 (GMT) Cc: current@FreeBSD.ORG In-Reply-To: <13804.10973.9290.919955@doom> from "D. Rock" at Sep 1, 98 07:32:19 pm X-Mailer: ELM [version 2.4 PL25] 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 > Recently, after a kernel panic the system behaves extremely strange: > Every time I reboot the machine, I *have* to fsck the / device (I > prefer the one / fits all approach), or any write access will result > to either "out of inodes" or "no space left on device" errors. > Each fsck will change the superblock (FREE BLK COUNT(S) WRONG IN > SUPERBLK). df -ki shows up even before the fsck plenty of inodes and > blocks left. This error only happens on the 1st drive in the system > (Seagate ST32122A), another one attached doesn't show up this > symptom. The partition table is OK (dangerous dedicated on both > drives, LBA mode set in the BIOS; fdisk/BIOS/in core disklabel agree). > I use flags 0x80ff for both drives (32-bit multiple (16) sector mode). > shutdown of the system seems to write all dirty blocks ("5 3 2 done") This is generally attributable to IDE. To see if your problem is real or imaginary, after fsck'ing the drive once (while mounted read-only), do it again. If you get the same thing (i.e., a drive doesn't stay fsck'ed when it should), then this is your problem. To resolve this problem, use as short an IDE cable as you possibly can; IDE is particularly sensitive to electrical interference, and requires short cables in the standard for this reason. Since EIDE is just IDE rehashed and given a facelift, this applies to EIDE as well. Note that you may actually be doing bad things to your disk contents with each fsck; it depends on just how noisy things are. Your best bet would be to get a shorer cable, back it up *now*, and then after reinstalling, restore from backup. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message