From owner-freebsd-current Mon Apr 26 11:44:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from mercury.ukc.ac.uk (mercury.ukc.ac.uk [129.12.21.10]) by hub.freebsd.org (Postfix) with ESMTP id 3A22D14C27 for ; Mon, 26 Apr 1999 11:44:21 -0700 (PDT) (envelope-from ayk1@ukc.ac.uk) Received: from ash.ukc.ac.uk ([129.12.3.224]) by mercury.ukc.ac.uk with smtp (Exim 2.12 #1) id 10bqKh-0000JW-00; Mon, 26 Apr 1999 19:42:19 +0100 Received: from localhost by ash.ukc.ac.uk (SMI-8.6/UKC-2.14) id TAA18822; Mon, 26 Apr 1999 19:44:17 +0100 Date: Mon, 26 Apr 1999 19:44:17 +0100 (BST) From: Alex To: Doug White Cc: freebsd-current@FreeBSD.ORG Subject: Re: file disappeared? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thank you for a quick response. > > pcayk:~/tmp$ df -k . > > Filesystem 1K-blocks Used Avail Capacity Mounted on > > /dev/wd0s1f 7621844 6975669 36428 99% /usr > > > > pcayk:~/tmp$ ls -l > > -rw-r--r-- 1 ayk1 users 716247040 Apr 22 1999 bigcdimage.iso > > > > pcayk:~/tmp$ rm bigcdimage.iso > > > > pcayk:~/tmp$ df -k . > > Filesystem 1K-blocks Used Avail Capacity Mounted on > > /dev/wd0s1f 7621844 6975669 36428 99% /usr > > > > How on earth did that happen?!!! > > Are you running soft updates? It takes ~30s for changes to take effect if > you are. I noticed this myself last week. I believe not - doesn't that involve adding a "SOFTUPDATES" option to the kernel? I don't have that in my kernel; therefore, disc access should be synchronous by default, right? And it had definitely been longer than 30s before I decided to run fsck (or before the first run completed). What does it all mean? That I have a file occupying 700+ Mb on my hard drive that I can't get rid of? :-( By the way, rm returned almost instantaneously - normally it takes a few seconds to remove such a huge file (that was the reason I even noticed the problem in the first place.) If this is a bug, I would be glad to help, but this kind of error is hard to reproduce... Perhaps someone with an in-depth knowledge of ufs can tell me what really happened (and what exactly did fsck do to my drive, just to make things worse.) > > So I decided to run fsck, with -p at first: > > > > > > pcayk:/usr/home/ayk1# fsck -p -f /dev/wd0s1f > > /dev/rwd0s1f: UNREF FILE I=1111053 OWNER=ayk1 MODE=100644 > > /dev/rwd0s1f: SIZE=716247040 MTIME=Apr 22 20:36 1999 (CLEARED) > > /dev/rwd0s1f: SUMMARY INFORMATION BAD (SALVAGED) > > /dev/rwd0s1f: BLK(S) MISSING IN BIT MAPS (SALVAGED) > > /dev/rwd0s1f: FREE BLK COUNT(S) WRONG IN SUPERBLK (SALVAGED) > > /dev/rwd0s1f: 176217 files, 6275813 used, 1346031 free (39575 frags, > > 163307 blocks, 0.5% fragmentation) > > I assume this was in single user mode, otherwise you made a gigantic mess. > :-) I did, didn't I? Alex --- A mathematician is a machine for converting coffee into theorems. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message