On Mon, 26 Apr 1999, Alex wrote: > > > 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).
If you're running default disk access then I'm guessing some program still has the file open. Perhaps 'cdrecord' hung? > > I assume this was in single user mode, otherwise you made a gigantic mess. > > :-) > > I did, didn't I? For the future, running fsck in multiuser mode is a no-no. Doug White Internet: dwh...@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
