From owner-freebsd-current Mon Oct 21 1:14: 9 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B594C37B401 for ; Mon, 21 Oct 2002 01:14:07 -0700 (PDT) Received: from relay1.cris.net (relay1.cris.net [212.110.128.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id D103643E88 for ; Mon, 21 Oct 2002 01:14:03 -0700 (PDT) (envelope-from phantom@phantom.cris.net) Received: from phantom.cris.net (root@phantom.cris.net [212.110.130.74]) by relay1.cris.net (8.12.6/8.12.4) with ESMTP id g9LBCiuU074822 for ; Mon, 21 Oct 2002 11:12:44 GMT (envelope-from phantom@phantom.cris.net) Received: (from phantom@localhost) by phantom.cris.net (8.12.2/8.12.2) id g9L8JHBC052609; Mon, 21 Oct 2002 11:19:17 +0300 (EEST) (envelope-from phantom) Date: Mon, 21 Oct 2002 11:19:17 +0300 From: Alexey Zelkin To: current@freebsd.org Subject: df problems ? Message-ID: <20021021111917.A52598@phantom.cris.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 4.5-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Folks, Two days ago I have hit into problem that make failed because of "disk full" error, but df(1) shown me that about 55% space at work slice is available. Check of this slice with du(1) shown that it's 100% utilized. I thought that it could be disk error - after manual execution of fsck(8) problem was solved, but after my boot into -CURRENT next time problem re-appeared. I have dual boot machine with -STABLE and -CURRENT (both have own boot slices and few slices are shared between them.) Both -CURRENT and -STABLE from 10 Oct. Kernel configuration is almost GENERIC (except removing some unneeded stuff.) Few slices have softupdates enabled, few disabled. Problem affects all of them. Following scenario is 100% reproducable here. 1. Run fsck in single user mode under -STABLE (Summary informaton fixed) 2. Run df -k (correct one, checked with du(1)) Filesystem 1K-blocks Used Avail Capacity Mounted on [..] /dev/ad0s1f 17026542 9821156 5843264 63% /home /dev/ad0s1e 4129310 415998 3382968 11% /usr/local [..] 3. immdiatelly reboot to -CURRENT Filesystem 1K-blocks Used Avail Capacity Mounted on [..] /dev/ad0s1f 17026542 3749466 11914954 24% /home /dev/ad0s1e 4129310 256922 3542044 7% /usr/local [..] 4. immediately reboot to -STABLE again Filesystem 1K-blocks Used Avail Capacity Mounted on [..] /dev/ad0s1f 17026542 3749466 11914954 24% /home /dev/ad0s1e 4129310 256922 3542044 7% /usr/local [..] Resume: problem appears after boot of -CURRENT and is permanent (even after reboot back to -STABLE) until fsck(8) executed. Anyone else seen it ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message