Skip site navigation (1)Skip section navigation (2)
Date:      Tue,  1 Sep 1998 19:32:19 +0200 (MET DST)
From:      "D. Rock" <rock@cs.uni-sb.de>
To:        current@FreeBSD.ORG
Subject:   What the fsck is going on here (disk space vanishing)?
Message-ID:  <13804.10973.9290.919955@doom>

next in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?13804.10973.9290.919955>