Fscking a live system is a Bad Idea(tm) and should be avoided. Reboot into single-user and fsck it manually (while unmounted).
Jason Young ANET Chief Network Engineer > -----Original Message----- > From: Alex [mailto:a...@ukc.ac.uk] > Sent: Monday, April 26, 1999 2:06 PM > To: Jason Young > Cc: Doug White; freebsd-current@FreeBSD.ORG > Subject: RE: file disappeared? > > > > > A file's storage isn't freed until its last reference is > removed. An open > > file descriptor is a reference. Do you perhaps have a hung CD > burner process > > or something similar running? > > > Nothing like that - I used a CD burner on another machine, and then ftp'ed > the image to my home dir in case I needed more copies. After a few days, > I decided that I didn't need it after all, and deleted it... or did I? > > The question is how badly did I screw things up by running fsck? > > It still reports > > pcayk:/etc# fsck -p -f /dev/wd0s1f > /dev/rwd0s1f: FREE BLK COUNT(S) WRONG IN SUPERBLK (SALVAGED) > /dev/rwd0s1f: SUMMARY INFORMATION BAD (SALVAGED) > /dev/rwd0s1f: BLK(S) MISSING IN BIT MAPS (SALVAGED) > /dev/rwd0s1f: 176225 files, 6278980 used, 1342864 free (39576 frags, > 162911 blocks, 0.5% fragmentation) > > (I think with -p it doesn't actually salvage anything, just checks the > disk). > > Worth a reboot? > > Alex > > --- > A mathematician is a machine for converting coffee into theorems. > > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
