From owner-freebsd-current Tue Sep 1 10:31:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA16546 for freebsd-current-outgoing; Tue, 1 Sep 1998 10:31:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA16498 for ; Tue, 1 Sep 1998 10:31:04 -0700 (PDT) (envelope-from rock@wurzelausix.cs.uni-sb.de) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.0/1998052000) with ESMTP id TAA26689 for ; Tue, 1 Sep 1998 19:30:02 +0200 (CEST) Received: from gate.ics (acc2-130.telip.uni-sb.de [134.96.112.130]) by cs.uni-sb.de (8.9.0/1998060300) with ESMTP id TAA15500 for ; Tue, 1 Sep 1998 19:30:02 +0200 (CEST) Received: from doom.ics (doom.ics [192.168.0.254]) by gate.ics (8.9.1/1998061600) with ESMTP id TAA22821 for ; Tue, 1 Sep 1998 19:24:26 +0200 (CEST) Received: (from rock@localhost) by doom.ics (8.8.8+Sun/8.8.8) id TAA02566; Tue, 1 Sep 1998 19:32:20 +0200 (MET DST) From: "D. Rock" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 1 Sep 1998 19:32:19 +0200 (MET DST) To: current@FreeBSD.ORG Subject: What the fsck is going on here (disk space vanishing)? X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13804.10973.9290.919955@doom> 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") Each time I delete some files (I deleted the complete /usr/obj tree), the new free space is also eaten up on reboot. I thought it maybe something wrong because I mounted the drive async while the kernel panic'd (i4b related, the system was idle at that time). After reboot the trouble began. fsck didn't find any error (besides the one above), so I thought something was severely hosed up. I dumped the entire system on another drive, booted from the 2nd one, newfs'd the 1st drive, restored anything back to the 1st drive and rebooted again. BANG! Same error again. I then noticed, that I "only" had to reboot to single user mode, "fsck /; exit" and the system is OK, but I wonder what the real error is. System is from Aug, 31 (just before E-Day), also tried to boot kernel.GENERIC (built on Aug, 21). Soft updates disabled (not compiled into the kernel, not set in the superblock) Any hints what is going on here? Daniel (I now changed in /etc/rc the line "fsck -p" to "fsck -y", but I hope there will be a better solution) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message