Hi there,
I reported a former heavy filesystem crash recently; have a look
at:
http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=846852+849687+/usr/local/www/db/text/2000/freebsd-current/20000123.freebsd-current
I got it again.
Meanwhile my system got updated to
FreeBSD abc.xyz.de 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Sat Jan 22 11:17:16 CET 2000
The system is complete soft-updates free.
This time I had no jailed processes running; the machine was idle
most of the time during the last few days and was rebooted (cleanly),
yesterday.
The (now totally hosed) file-system was mounted thru the following
fstab-entry:
/dev/da1s1g /scratch ufs rw 2 2
Today I incidentally noticed that the directory /scratch was
empty all of the sudden.
I should have found various sub-directories, especially since
I built the world on this disk a few days ago.
Nonetheless 'df' showed the filesystem as 45% filled.
I was able to unmount and mount the filesystem without(!!) an error.
There were definately no related messages in the logs or on the
console.
Starting an 'fsck' results in:
cage:[/] # fsck /scratch
** /dev/da1s1g
** Last Mounted on /scratch
** Phase 1 - Check Blocks and Sizes
PARTIALLY TRUNCATED INODE I=16
SALVAGE? [yn] ^C
***** FILE SYSTEM MARKED DIRTY *****
I interrupted the fsck-run as soon as I decided that it might be
advisable to leave it in its hosed state just for the case that
there is some illuminated filesystem-hacker who would like to
take a peek. (I would allow ssh-access to the box ...)
Bye,
Andreas
--
Andreas Braukmann - private site -
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
